Triple
T14273193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nice urban public transport network |
E353844
|
entity |
| Predicate | primaryModes |
P113527
|
FINISHED |
| Object | tram |
—
|
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: tram | Statement: [Nice urban public transport network, primaryModes, tram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryModes Context triple: [Nice urban public transport network, primaryModes, tram]
-
A.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
B.
primaryCharacteristics
Indicates the main defining traits or features that most fundamentally characterize an entity.
-
C.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
D.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de65811d7c8190b075909a6570d415 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.