Triple
T8720590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tourangeau |
E206999
|
entity |
| Predicate | coordinateTerm |
P84262
|
FINISHED |
| Object | Parisien |
—
|
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: Parisien | Statement: [Tourangeau, coordinateTerm, Parisien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateTerm Context triple: [Tourangeau, coordinateTerm, Parisien]
-
A.
positionTerm
Indicates that one entity holds, is assigned, or is described by a specific role, title, or positional designation in relation to another entity.
-
B.
coordinateExpression
Indicates that one expression is syntactically or semantically coordinated with another, typically as part of a compound structure (e.g., joined by "and" or "or").
-
C.
coordinateSymbols
Indicates a relationship where one symbol is aligned or matched with another symbol in a coordinated or corresponding way.
-
D.
coordinateOn
Indicates that two or more entities work together to organize, align, or manage a shared activity, process, or objective.
-
E.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d02a52c81909f93622ae6920b80 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.