Triple
T3037196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Joint Force Command Naples |
E83038
|
entity |
| Predicate | dateReorganizedAsJFC |
P40645
|
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: [Allied Joint Force Command Naples, dateReorganizedAsJFC, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReorganizedAsJFC Context triple: [Allied Joint Force Command Naples, dateReorganizedAsJFC, 2004]
-
A.
formerFixedDate
Indicates that a previously established specific date associated with an event or relationship has changed and is no longer current.
-
B.
furtherReorganizedOn
chosen
Indicates that an entity was reorganized again or to a greater extent on a specified later date or occasion.
-
C.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2cd4988190b52fe3616ecbe9ef |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.