Triple
T15786278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koobi Fora |
E382745
|
entity |
| Predicate | significantFind |
P39927
|
FINISHED |
| Object | Homo habilis fossils |
—
|
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: Homo habilis fossils | Statement: [Koobi Fora, significantFind, Homo habilis fossils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantFind Context triple: [Koobi Fora, significantFind, Homo habilis fossils]
-
A.
notableFinding
chosen
Indicates that an observation, result, or piece of evidence is considered significant or noteworthy in the given context.
-
B.
significantPort
Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
-
C.
significantDevelopment
Indicates a development, change, or event that has substantial impact or importance within a given context or process.
-
D.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
E.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0540380448190a025338f0e62e6d1 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.