Triple
T1277648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herodian enclosure |
E27250
|
entity |
| Predicate | wallTechnique |
P25296
|
FINISHED |
| Object | precisely cut stones without mortar |
—
|
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: precisely cut stones without mortar | Statement: [Herodian enclosure, wallTechnique, precisely cut stones without mortar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallTechnique Context triple: [Herodian enclosure, wallTechnique, precisely cut stones without mortar]
-
A.
wallTreatment
Indicates how a wall is finished, covered, or treated in terms of its surface appearance or protective coating.
-
B.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
-
C.
hasOutfieldWallCovering
Indicates that an outfield wall is covered or surfaced with a particular material or type of covering.
-
D.
hasWallShape
Indicates that an entity possesses a wall whose form or outline matches a specified geometric or structural shape.
-
E.
hasWallType
chosen
Indicates the specific kind or classification of wall associated with an 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.