Triple
T9441788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southern wing of the Cour Carrée |
E227662
|
entity |
| Predicate | courtyardRelation |
P88908
|
FINISHED |
| Object | southern side of the Cour Carrée |
—
|
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: southern side of the Cour Carrée | Statement: [southern wing of the Cour Carrée, courtyardRelation, southern side of the Cour Carrée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtyardRelation Context triple: [southern wing of the Cour Carrée, courtyardRelation, southern side of the Cour Carrée]
-
A.
courtyardType
Indicates the specific kind or classification of a courtyard associated with an entity.
-
B.
courtyardShape
Indicates the geometric form or configuration that characterizes a courtyard.
-
C.
courtyardName
Indicates that an entity has a specific name assigned to a courtyard.
-
D.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
E.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ee4f4a08190ada5ee14fec2b822 |
completed | April 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:50 p.m.