Triple
T18671279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equipe Unifiée de l’ex-URSS |
E456481
|
entity |
| Predicate | timeLimitedEntity |
P12795
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Equipe Unifiée de l’ex-URSS, timeLimitedEntity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLimitedEntity Context triple: [Equipe Unifiée de l’ex-URSS, timeLimitedEntity, true]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
timeAfterAble
Indicates that one event, state, or action occurs after another point in time at which it becomes possible or permissible.
-
C.
timeToControl
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
D.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
-
E.
timeExistence
chosen
Indicates the period or duration during which an entity exists or is valid.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b21d2481908e1b8b583bfabb72 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.