Triple
T16842958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just a Minute (India) |
E409458
|
entity |
| Predicate | coreSkillTested |
P53725
|
FINISHED |
| Object | fluency in speech |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: fluency in speech | Statement: [Just a Minute (India), coreSkillTested, fluency in speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreSkillTested Context triple: [Just a Minute (India), coreSkillTested, fluency in speech]
-
A.
skillAssessed
chosen
Indicates that an entity’s skill or competency has been evaluated or measured, typically by another agent or process.
-
B.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
C.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
D.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
E.
validatesSkill
Indicates that one entity confirms or verifies the authenticity, correctness, or adequacy of another entity’s skill or competency.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b35284588190a1d6238438f3e70d |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.