Triple
T21482617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Rondavels |
E530032
|
entity |
| Predicate | numberOfFormations |
P144532
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Three Rondavels, numberOfFormations, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfFormations Context triple: [Three Rondavels, numberOfFormations, 3]
-
A.
hasFiveMajorFormations
Indicates that an entity possesses or is associated with exactly five primary or principal formations.
-
B.
appliesToFormationNumber
Indicates that something (such as a rule, condition, or attribute) is specifically associated with or relevant to a particular formation number.
-
C.
supportedFormation
Indicates that one entity provided assistance, resources, or conditions that enabled the creation or establishment of another entity or structure.
-
D.
bandFormation
Indicates the event or process by which a musical band is created or comes together as a group.
-
E.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea34c4388190adc78d209d2aafb8 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:21 p.m.