Triple
T683003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Empire |
E13221
|
entity |
| Predicate | typicalPlanType |
P8653
|
FINISHED |
| Object | rectangular plan |
—
|
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: rectangular plan | Statement: [Second Empire, typicalPlanType, rectangular plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlanType Context triple: [Second Empire, typicalPlanType, rectangular plan]
-
A.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
B.
offersPlanType
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
-
C.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
D.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a070d4c08190a510a8f9c1ae8076 |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.