Triple
T27271226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo luzonensis |
E688055
|
entity |
| Predicate | foundInCaveSystem |
P125269
|
FINISHED |
| Object | Callao Cave system |
—
|
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: Callao Cave system | Statement: [Homo luzonensis, foundInCaveSystem, Callao Cave system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInCaveSystem Context triple: [Homo luzonensis, foundInCaveSystem, Callao Cave system]
-
A.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
B.
isInCavernSystem
chosen
Indicates that one entity is located within or forms part of an interconnected network of underground caverns associated with another entity.
-
C.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
D.
caveType
Indicates the specific classification or kind of cave associated with an entity.
-
E.
hasCaveEntranceDepth
Indicates the depth or vertical distance of a cave’s entrance relative to a reference level (such as ground surface or sea level).
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 10:59 a.m.