Triple
T24295272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union officials |
E605941
|
entity |
| Predicate | alsoWorkIn |
P105030
|
FINISHED |
| Object | Strasbourg |
—
|
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: Strasbourg | Statement: [European Union officials, alsoWorkIn, Strasbourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoWorkIn Context triple: [European Union officials, alsoWorkIn, Strasbourg]
-
A.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
B.
laterWorksAt
Indicates that an entity begins working at a place or organization at a time later than another referenced time or employment situation.
-
C.
otherWork
Indicates that one work is related to another work by the same creator, but is distinct from the primary or referenced work.
-
D.
hasWorksIn
chosen
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.