Triple
T20549630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Rey archaeological site |
E504562
|
entity |
| Predicate | primaryConstructionTechnique |
P625
|
FINISHED |
| Object | masonry |
—
|
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: masonry | Statement: [El Rey archaeological site, primaryConstructionTechnique, masonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConstructionTechnique Context triple: [El Rey archaeological site, primaryConstructionTechnique, masonry]
-
A.
constructionTechniqueComparedTo
Indicates a relationship where one construction technique is evaluated or contrasted against another in terms of method, quality, efficiency, or other relevant criteria.
-
B.
constructionMethod
chosen
Indicates the technique or process by which something is built, assembled, or created.
-
C.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
D.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
E.
describesConstructionOf
Indicates that one entity provides information or details about how another entity is built, formed, or constructed.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5d739bc8190b2bf60f82d2ade0c |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.