Triple
T33997852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L9 Nord |
E871724
|
entity |
| Predicate | sharesLineNumberWith |
P120966
|
FINISHED |
| Object | L9 Sud |
—
|
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: L9 Sud | Statement: [L9 Nord, sharesLineNumberWith, L9 Sud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLineNumberWith Context triple: [L9 Nord, sharesLineNumberWith, L9 Sud]
-
A.
sharesLineUpWith
Indicates that two entities participate together in the same lineup or roster at the same time.
-
B.
sharesNumberWith
chosen
Indicates that two entities have the same numerical value or share an identical number.
-
C.
sharesTrunkLineWith
Indicates that two entities are connected to or use the same primary communication or utility trunk line.
-
D.
sharesTelephonePartyLineWith
Indicates that two entities use the same shared telephone party line for their calls.
-
E.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 1, 2026, 1:50 a.m.