Triple
T26410630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue Franklin D. Roosevelt |
E663948
|
entity |
| Predicate | hasNotableSquareNearby |
P39585
|
FINISHED |
| Object | Place Clemenceau |
—
|
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: Place Clemenceau | Statement: [Avenue Franklin D. Roosevelt, hasNotableSquareNearby, Place Clemenceau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSquareNearby Context triple: [Avenue Franklin D. Roosevelt, hasNotableSquareNearby, Place Clemenceau]
-
A.
hasNearbySquare
Indicates that one entity has at least one square-shaped entity located close to it in space.
-
B.
hasNotableNearbyEntity
chosen
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
C.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
-
D.
hasNearbyMine
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
E.
hasFortificationNearby
Indicates that one entity is located in proximity to, or within the immediate area of, a fortification structure associated with it.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 26, 2026, 11:37 p.m.