Triple
T3043629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unfinished Obelisk |
E83188
|
entity |
| Predicate | visibleFeatures |
P25983
|
FINISHED |
| Object | cracks along the shaft |
—
|
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: cracks along the shaft | Statement: [Unfinished Obelisk, visibleFeatures, cracks along the shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleFeatures Context triple: [Unfinished Obelisk, visibleFeatures, cracks along the shaft]
-
A.
displaysFeature
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
visibleRemains
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
D.
visualFeature
chosen
Indicates a relationship where one entity possesses or exhibits a particular visual characteristic or attribute of another entity.
-
E.
visibleAtSurface
Indicates that something can be seen or is observable at the outer surface of an object or medium.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b5ec5988190b8b6c95c743c6d1e |
completed | March 8, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.