Triple
T7302829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EURO |
E167898
|
entity |
| Predicate | mostRecentExpansion |
P59994
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [EURO, mostRecentExpansion, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostRecentExpansion Context triple: [EURO, mostRecentExpansion, 2016]
-
A.
significantExpansionDate
chosen
Indicates the date on which an entity underwent a major or notable expansion in its size, scope, or operations.
-
B.
majorExpansionUnder
Indicates that one entity is undergoing or has undergone a significant enlargement, growth, or extension while being under the authority, control, or scope of another entity.
-
C.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
D.
estimatedInitialExpansionDate
Indicates the date on which the initial expansion of something (such as a project, system, or operation) is estimated to have begun or will begin.
-
E.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.