Triple
T1085247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tura limestone |
E24034
|
entity |
| Predicate | typicalUseLocationOnMonument |
P21833
|
FINISHED |
| Object | outer surfaces |
—
|
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: outer surfaces | Statement: [Tura limestone, typicalUseLocationOnMonument, outer surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseLocationOnMonument Context triple: [Tura limestone, typicalUseLocationOnMonument, outer surfaces]
-
A.
typicalUseLocation
chosen
Indicates the usual or most common location where an entity is used or operates.
-
B.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
C.
hasInitialPointMonument
Indicates that a monument serves as the designated initial or starting point for a referenced spatial feature or boundary.
-
D.
memorialLocatedAt
Indicates that a memorial is situated or found at a specific location.
-
E.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b961d0cc8190858296b44fab2f32 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.