Triple
T25296723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khaidi No. 150 |
E634234
|
entity |
| Predicate | featuresItemNumber |
P54721
|
FINISHED |
| Object | special song appearance by Lakshmi Rai |
—
|
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: special song appearance by Lakshmi Rai | Statement: [Khaidi No. 150, featuresItemNumber, special song appearance by Lakshmi Rai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresItemNumber Context triple: [Khaidi No. 150, featuresItemNumber, special song appearance by Lakshmi Rai]
-
A.
featuresItem
chosen
Indicates that one entity includes, presents, or highlights another entity as a notable item or component.
-
B.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
C.
modelNumber
Indicates that one entity is the specific model identifier or code assigned to another entity (such as a product or device).
-
D.
articleNumber
Indicates that one entity is identified or referenced by a specific article number assigned to it.
-
E.
specNumber
Indicates that an entity is associated with a specific specification identifier or number.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 1:22 p.m.