Triple
T37742212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir |
E940745
|
entity |
| Predicate | recordHolderForLongestSingleStay |
P40964
|
FINISHED |
| Object | Valeri Polyakov |
—
|
NE NERFINISHED |
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: Valeri Polyakov | Statement: [Mir, recordHolderForLongestSingleStay, Valeri Polyakov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordHolderForLongestSingleStay Context triple: [Mir, recordHolderForLongestSingleStay, Valeri Polyakov]
-
A.
lengthOfStay
Indicates the duration of time that an entity remains at or within a particular place, service, or state.
-
B.
longestDurationAt
chosen
Indicates that one entity has the greatest length of time associated with a particular state, event, or activity compared to other relevant entities.
-
C.
venueResidencyLengthNights
Indicates the number of nights an entity stays or is scheduled to stay at a particular venue.
-
D.
recordHeldDuration
Indicates the length of time for which a particular record, title, or achievement was continuously held.
-
E.
heldLongestSpanRecordUntil
Indicates that one entity held the record for the longest continuous span of time in some domain or metric, up until a specified endpoint or event.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:18 p.m.