Triple
T35650871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eiffel Bridge |
E1030142
|
entity |
| Predicate | spanOver |
P141782
|
FINISHED |
| Object | Onyar River |
—
|
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: Onyar River | Statement: [Eiffel Bridge, spanOver, Onyar River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spanOver Context triple: [Eiffel Bridge, spanOver, Onyar River]
-
A.
spanType
Indicates the specific category or kind of span that characterizes the relationship or action between entities.
-
B.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
-
C.
splitOver
Indicates that something is divided or separated into parts that are distributed across multiple items, areas, or time periods.
-
D.
spansTo
chosen
Indicates that one entity extends across or covers a continuous range up to another entity or boundary.
-
E.
leafSpan
Indicates the extent or range covered by a leaf, such as its length, width, or overall spread.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f745ec08190bb404b90e0c05fb4 |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.