Triple
T27348008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo floresiensis |
E684280
|
entity |
| Predicate | earliestKnownAgeYearsAgo |
P87250
|
FINISHED |
| Object | 100000 |
—
|
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: 100000 | Statement: [Homo floresiensis, earliestKnownAgeYearsAgo, 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestKnownAgeYearsAgo Context triple: [Homo floresiensis, earliestKnownAgeYearsAgo, 100000]
-
A.
isEarliestAgeOf
Indicates that one value represents the minimum or first age at which a specified condition, event, or state occurs for an entity.
-
B.
oldestAge
Indicates that the associated value represents the greatest (maximum) age within a given group, set, or context.
-
C.
earliestKnownPeriod
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
D.
approximateStartAge
chosen
Indicates the estimated or roughly determined age at which an event, condition, or state begins.
-
E.
typicallyIssuedAtAge
Indicates the age at which something is most commonly or customarily issued to an individual.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 11:46 a.m.