Triple
T31125387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antoine Gili |
E793342
|
entity |
| Predicate | workLocatedIn |
P1527
|
FINISHED |
| Object | Vence |
—
|
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: Vence | Statement: [Antoine Gili, workLocatedIn, Vence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLocatedIn Context triple: [Antoine Gili, workLocatedIn, Vence]
-
A.
locationInWork
Indicates that one entity specifies the place or setting where another entity occurs, is situated, or takes place within a particular work (e.g., a scene’s location in a film or a chapter’s setting in a book).
-
B.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
C.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
-
D.
residesInWork
Indicates that a person or entity lives or is based within the location, setting, or environment defined by a particular work (such as a book, film, or other creative piece).
-
E.
organizationLocatedAt
Indicates that an organization is situated or based at a specific geographic location or address.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.