Triple
T14795526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue Hoche |
E347765
|
entity |
| Predicate | hasNumberingStart |
P116134
|
FINISHED |
| Object | Place Charles-de-Gaulle side |
—
|
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: Place Charles-de-Gaulle side | Statement: [Avenue Hoche, hasNumberingStart, Place Charles-de-Gaulle side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberingStart Context triple: [Avenue Hoche, hasNumberingStart, Place Charles-de-Gaulle side]
-
A.
hasNumberingRole
Indicates that an entity holds a specific role or responsibility related to assigning, managing, or using numbers within a given context.
-
B.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
C.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
E.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90c5e3a08190868680b081308c1d |
completed | April 14, 2026, 7:08 p.m. |
Created at: April 10, 2026, 1:31 a.m.