Triple
T25872860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchnadamph Bone Caves |
E651804
|
entity |
| Predicate | containsRemainsFromPeriod |
P137162
|
FINISHED |
| Object | Pleistocene |
—
|
NE NERFINISHED |
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: Pleistocene | Statement: [Inchnadamph Bone Caves, containsRemainsFromPeriod, Pleistocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRemainsFromPeriod Context triple: [Inchnadamph Bone Caves, containsRemainsFromPeriod, Pleistocene]
-
A.
containsMaterialFromPeriod
chosen
Indicates that something includes material originating from or associated with a specified historical or temporal period.
-
B.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
C.
survivesFromPeriod
Indicates that an entity continues to exist or remain intact from a specified historical or temporal period into a later time.
-
D.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
E.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 22, 2026, 8:11 a.m.