Triple
T38543884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vindija Cave |
E924911
|
entity |
| Predicate | hasDating |
P191182
|
FINISHED |
| Object | Late Pleistocene |
—
|
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: Late Pleistocene | Statement: [Vindija Cave, hasDating, Late Pleistocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDating Context triple: [Vindija Cave, hasDating, Late Pleistocene]
-
A.
hasBeenDatedBy
Indicates that one entity has previously been in a romantic or dating relationship with another entity.
-
B.
usedForDating
Indicates a relationship where one entity is used as a means, tool, or context for engaging in romantic or dating activities with another entity.
-
C.
wasInRelationshipDuring
Indicates that two entities were in a romantic or otherwise defined interpersonal relationship with each other during a specified time period.
-
D.
hadPartner
Indicates that an entity was in a romantic or life-partner relationship with another entity at some point in time.
-
E.
hasOnlineDatingElement
Indicates that the relationship or situation involves some aspect or component of online dating.
- F. None of above. chosen
Provenance (4 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.