Triple
T5004051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de la Bâtie |
E112442
|
entity |
| Predicate | hasFunctionInPresent |
P61430
|
FINISHED |
| Object | tourist attraction |
—
|
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: tourist attraction | Statement: [Château de la Bâtie, hasFunctionInPresent, tourist attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInPresent Context triple: [Château de la Bâtie, hasFunctionInPresent, tourist attraction]
-
A.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
B.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
-
C.
hasFunctionInPlot
Indicates that an entity serves a particular role or purpose within the structure or progression of a plot.
-
D.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
-
E.
hasFunctionInScore
Indicates that an entity serves a specific functional role within a musical score.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd74713fc88190916c2b04cd2e677e |
completed | March 20, 2026, 4:23 p.m. |
Created at: March 20, 2026, 1:35 p.m.