Triple
T33457894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit Khallaf |
E856826
|
entity |
| Predicate | hasSubstructureFeature |
P195228
|
FINISHED |
| Object | multiple chambers |
—
|
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 chambers | Statement: [Beit Khallaf, hasSubstructureFeature, multiple chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubstructureFeature Context triple: [Beit Khallaf, hasSubstructureFeature, multiple chambers]
-
A.
containsAsSubstructure
Indicates that one structure includes another structure entirely within it as a component or embedded part.
-
B.
hasStructuralSubtype
Indicates that one structure is a more specific, subordinate form or subtype of another structure within a structural hierarchy.
-
C.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
D.
hasSubproperty
Indicates that one property is a more specific version of another property, inheriting its meaning and constraints.
-
E.
hasStructuralCharacter
chosen
Indicates that one entity possesses a particular structural property, form, or configuration that characterizes it.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 1, 2026, 1:37 a.m.