Triple
T4787533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taga Stone Quarry |
E106517
|
entity |
| Predicate | hasTypeOfStructure |
P841
|
FINISHED |
| Object | megalithic remains |
—
|
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: megalithic remains | Statement: [Taga Stone Quarry, hasTypeOfStructure, megalithic remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfStructure Context triple: [Taga Stone Quarry, hasTypeOfStructure, megalithic remains]
-
A.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
E.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65da229c81909c703393f7b9b71d |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.