Triple
T32657145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terwilliger |
E834892
|
entity |
| Predicate | notableBearerSpecies |
P205131
|
FINISHED |
| Object | human (fictional) |
—
|
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: human (fictional) | Statement: [Terwilliger, notableBearerSpecies, human (fictional)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerSpecies Context triple: [Terwilliger, notableBearerSpecies, human (fictional)]
-
A.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
C.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
D.
habitatOfNotableSpecies
Indicates that a location serves as the natural environment or living area for one or more notable species.
-
E.
notableSpeciesRole
Indicates that a species plays a particularly important, characteristic, or influential role in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:08 a.m.