Triple
T33022515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marayoor |
E844949
|
entity |
| Predicate | hasPrehistoricRemains |
P33395
|
FINISHED |
| Object | dolmens |
—
|
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: dolmens | Statement: [Marayoor, hasPrehistoricRemains, dolmens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrehistoricRemains Context triple: [Marayoor, hasPrehistoricRemains, dolmens]
-
A.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
B.
hasArchaeologicalFeature
chosen
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
C.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
D.
hasArchaeologicalExcavationsSince
Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
-
E.
hasArchaeologicalMaterial
Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: May 1, 2026, 1:23 a.m.