Triple
T16926172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AP1000 |
E410578
|
entity |
| Predicate | containmentFeature |
P29386
|
FINISHED |
| Object | concrete shield building |
—
|
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: concrete shield building | Statement: [AP1000, containmentFeature, concrete shield building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containmentFeature Context triple: [AP1000, containmentFeature, concrete shield building]
-
A.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
B.
isFeatureOf
chosen
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
C.
hasContainment
Indicates that one entity spatially or logically encloses, includes, or holds another within its bounds.
-
D.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
E.
nestFeature
Indicates that one entity is a structural or functional component contained within, or forming part of, another entity.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdf2dcd881909798bd245e18c599 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.