Triple
T2211531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Obelisk (Cleopatra's Needle) |
E50926
|
entity |
| Predicate | hasBaseMaterial |
P1272
|
FINISHED |
| Object | granite pedestal |
—
|
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: granite pedestal | Statement: [The Obelisk (Cleopatra's Needle), hasBaseMaterial, granite pedestal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseMaterial Context triple: [The Obelisk (Cleopatra's Needle), hasBaseMaterial, granite pedestal]
-
A.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
B.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
hasBasedUnit
Indicates that something is defined or measured in terms of a specified base unit.
-
D.
appliedToMaterial
Indicates that an action, process, or treatment is performed on or directed toward a specific material.
-
E.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfecea6c8190b762bbfda8490e31 |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.