Triple
T10172015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Don’t Know |
E235352
|
entity |
| Predicate | hasTypeOfNumber |
P4426
|
FINISHED |
| Object | ensemble number |
—
|
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: ensemble number | Statement: [You Don’t Know, hasTypeOfNumber, ensemble number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfNumber Context triple: [You Don’t Know, hasTypeOfNumber, ensemble number]
-
A.
typeOf
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
B.
hasNumberCategory
chosen
Indicates that an entity is associated with a specific numerical classification or type.
-
C.
hasTypeOfReference
Indicates that one entity uses or is associated with a particular kind or category of reference (such as a citation, pointer, or referential link) to another entity.
-
D.
hasNumberOfTypes
Indicates that an entity is associated with a specific count of distinct types or categories it possesses or includes.
-
E.
hasTypeOfNames
Indicates that one entity possesses or is associated with a particular category or kind of names defined by another entity.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9e4e0c819097dceb7bf7757948 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.