Triple
T399945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Round Church |
E9256
|
entity |
| Predicate | hasPlan |
P10988
|
FINISHED |
| Object | circular nave with surrounding aisle |
—
|
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: circular nave with surrounding aisle | Statement: [Round Church, hasPlan, circular nave with surrounding aisle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlan Context triple: [Round Church, hasPlan, circular nave with surrounding aisle]
-
A.
hasGlobalPlan
Indicates that an entity possesses or is associated with an overarching, comprehensive plan that applies at a global or system-wide level.
-
B.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
offersPlanType
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
-
E.
planType
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8e655c819081eff85c0ef55fa5 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea4545608190898436c72e10f39d |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.