Triple
T5283136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cella (naos) |
E119546
|
entity |
| Predicate | typicalPlan |
P8653
|
FINISHED |
| Object | rectangular room |
—
|
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 room | Statement: [cella (naos), typicalPlan, rectangular room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlan Context triple: [cella (naos), typicalPlan, rectangular room]
-
A.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
B.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
C.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
D.
bodyPlan
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.