Triple
T26749019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trigance |
E674480
|
entity |
| Predicate | Château de TriganceInstanceOf |
P161194
|
FINISHED |
| Object | medieval castle |
—
|
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: medieval castle | Statement: [Trigance, Château de TriganceInstanceOf, medieval castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Château de TriganceInstanceOf Context triple: [Trigance, Château de TriganceInstanceOf, medieval castle]
-
A.
associatedWithChâteau
Indicates a relationship in which an entity is linked or connected to a particular château, such as by ownership, location, origin, or other relevant association.
-
B.
includesChâteau
Indicates that one entity contains, comprises, or features a château as part of its composition, membership, or contents.
-
C.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
D.
castleLocatedIn
Indicates that a castle is situated within or belongs to a specific geographic or administrative location.
-
E.
Château de Florac_use
Indicates how the Château de Florac is or has been used or functioned (e.g., its role, purpose, or utilization).
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61887c16c81909fc5bb18ae427834 |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:52 a.m.