Triple
T27348006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo floresiensis |
E684280
|
entity |
| Predicate | estimatedLastAppearanceMa |
P16814
|
FINISHED |
| Object | 0.05 |
—
|
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: 0.05 | Statement: [Homo floresiensis, estimatedLastAppearanceMa, 0.05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedLastAppearanceMa Context triple: [Homo floresiensis, estimatedLastAppearanceMa, 0.05]
-
A.
lastRegularAppearanceDate
Indicates the date on which an entity made its most recent standard or non-special appearance.
-
B.
lastAppearance
chosen
Indicates the most recent time or instance in which an entity appears or is present within a given context or sequence.
-
C.
lastSeen
Indicates the most recent time or occasion on which one entity observed, encountered, or had contact with another entity.
-
D.
lastSeenOn
Indicates the most recent time or date at which the subject entity was observed, detected, or recorded.
-
E.
lastSeenBy
Indicates that an entity was most recently observed, detected, or recorded by a particular agent or source.
- 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.