Triple
T3277170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collège Bourbon |
E68784
|
entity |
| Predicate | historicalNameType |
P47064
|
FINISHED |
| Object | collège |
—
|
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: collège | Statement: [Collège Bourbon, historicalNameType, collège]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameType Context triple: [Collège Bourbon, historicalNameType, collège]
-
A.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
B.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
C.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
D.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
E.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0128f08819084644f3c8fda2596 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.