Triple
T7552322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 16 |
E178566
|
entity |
| Predicate | hasBuildingPhaseCount |
P37745
|
FINISHED |
| Object | multiple superimposed phases |
—
|
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: multiple superimposed phases | Statement: [Temple 16, hasBuildingPhaseCount, multiple superimposed phases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingPhaseCount Context triple: [Temple 16, hasBuildingPhaseCount, multiple superimposed phases]
-
A.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
B.
hasMultiplePhases
chosen
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
C.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
D.
hasBuildingForm
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
-
E.
constructionPhase
Indicates the specific stage or period an entity is in within an overall construction or building process.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b6c6488190b8fd94aca6ea8486 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.