Triple
T25964739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bending Spoons |
E645634
|
entity |
| Predicate | laterHeadquarteredIn |
P120562
|
FINISHED |
| Object | Milan |
—
|
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: Milan | Statement: [Bending Spoons, laterHeadquarteredIn, Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHeadquarteredIn Context triple: [Bending Spoons, laterHeadquarteredIn, Milan]
-
A.
movedHeadquartersAfter
Indicates that one entity relocated its main headquarters to a new place or organization after a point in time or event associated with another entity.
-
B.
relocatedCompanyHeadquartersTo
Indicates that a company moved its main headquarters from a previous location to a new specified location.
-
C.
movedHeadquartersFrom
Indicates that an entity relocated its main headquarters from one specified place to another.
-
D.
laterCompanyHeadquartersCity
chosen
Indicates that the specified city is the location of a company’s headquarters during a later period in time, following an earlier headquarters location.
-
E.
headquartersPreviousLocation
Indicates that an entity’s headquarters used to be located at a specified place before moving to its current location.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 8:48 a.m.