Triple
T12698689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsh Arab culture |
E303400
|
entity |
| Predicate | includesArchitectureType |
P4631
|
FINISHED |
| Object | mudhif |
—
|
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: mudhif | Statement: [Marsh Arab culture, includesArchitectureType, mudhif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesArchitectureType Context triple: [Marsh Arab culture, includesArchitectureType, mudhif]
-
A.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
B.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
D.
usesArchitectureComponent
Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
-
E.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.