Triple
T19163926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Monument |
E469127
|
entity |
| Predicate | hasRockQuality |
P66351
|
FINISHED |
| Object | generally solid Wingate sandstone |
—
|
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: generally solid Wingate sandstone | Statement: [Independence Monument, hasRockQuality, generally solid Wingate sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockQuality Context triple: [Independence Monument, hasRockQuality, generally solid Wingate sandstone]
-
A.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
stoneQuality
chosen
Indicates the quality or grade assigned to a stone in terms of its characteristics or condition.
-
C.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
D.
hasRockArchName
Indicates that a rock arch is associated with a specific name or designation.
-
E.
hasRockyTerrain
Indicates that the subject possesses or is characterized by rough, uneven, or rock-covered ground or surface conditions.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebeb9848190ad4ae4c61fa14e08 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.