Triple
T31939428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union |
E815483
|
entity |
| Predicate | hasEnlargementYear |
P188898
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [European Union, hasEnlargementYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnlargementYear Context triple: [European Union, hasEnlargementYear, 2004]
-
A.
hadGrowthPeriod
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
B.
hasAtLargeFormatSince
Indicates that an entity has been available or operating in a large-format version starting from a specified point in time.
-
C.
expandedSignificantlyInYear
Indicates that an entity underwent a substantial increase or growth during a specified year.
-
D.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
-
E.
hasEnlargementPolicy
Indicates that an entity defines or is governed by a policy specifying how it may expand, grow, or be enlarged over time.
- F. None of above. chosen
Provenance (4 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 12:05 a.m.