Triple
T27281394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo antecessor |
E688340
|
entity |
| Predicate | knownFromSite |
P30061
|
FINISHED |
| Object | Gran Dolina |
—
|
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: Gran Dolina | Statement: [Homo antecessor, knownFromSite, Gran Dolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownFromSite Context triple: [Homo antecessor, knownFromSite, Gran Dolina]
-
A.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
knownToBe
Indicates that one entity is recognized or acknowledged as being a certain way, having a certain property, or fitting a particular description by others.
-
D.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
E.
bestKnownAsSiteOf
chosen
Indicates that a place is most widely recognized or famous for being the location where a particular event, activity, or feature occurs or is found.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 11:07 a.m.