Triple
T16332549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenoble tramway |
E396589
|
entity |
| Predicate | reintroductionOf |
P18106
|
FINISHED |
| Object | historic Grenoble tramway |
—
|
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: historic Grenoble tramway | Statement: [Grenoble tramway, reintroductionOf, historic Grenoble tramway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintroductionOf Context triple: [Grenoble tramway, reintroductionOf, historic Grenoble tramway]
-
A.
reintroduced
chosen
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
B.
reintroducedSpecies
Indicates that a species has been brought back and established again in an area where it had previously disappeared or been extirpated.
-
C.
reintroducedFrom
Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
-
D.
proposedReintroductionSite
Indicates that a location has been identified or suggested as a candidate site for reintroducing a species or population.
-
E.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e0b1388190824b286e8452fb32 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.