Triple
T16273715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Valère |
E395068
|
entity |
| Predicate | organDatingFrom |
P54278
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Château de Valère, organDatingFrom, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organDatingFrom Context triple: [Château de Valère, organDatingFrom, 15th century]
-
A.
organDatingFromCentury
chosen
Indicates that an organ is dated to or originates from a specified century.
-
B.
scientificDating
Indicates that an object or material has been assigned an age or time period using scientific dating methods (e.g., radiocarbon, dendrochronology, or other analytical techniques).
-
C.
likelyDatingFrom
Indicates that something is estimated or believed to originate from, or have begun in, a particular time period or date.
-
D.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
E.
hasBeenDatedBy
Indicates that one entity has previously been in a romantic or dating relationship with another entity.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460b22d88190bdc7cf509cf74198 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.