Triple
T10030037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponts |
E204827
|
entity |
| Predicate | historicalSpecialization |
P91784
|
FINISHED |
| Object | bridges |
—
|
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: bridges | Statement: [Ponts, historicalSpecialization, bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSpecialization Context triple: [Ponts, historicalSpecialization, bridges]
-
A.
primaryHistoricalSpecialism
Indicates that one entity’s main area of expertise or focus is a particular historical field or period.
-
B.
historicalDiscipline
Indicates that one entity is a field or branch of academic study within the broader domain of history in relation to another entity.
-
C.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
D.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
E.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde7ec088190845656cc2529c771 |
completed | April 2, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:54 p.m.