Triple
T26921387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauropsida |
E677653
|
entity |
| Predicate | replacedTermInSomeClassifications |
P34752
|
FINISHED |
| Object | Reptilia |
—
|
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: Reptilia | Statement: [Sauropsida, replacedTermInSomeClassifications, Reptilia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedTermInSomeClassifications Context triple: [Sauropsida, replacedTermInSomeClassifications, Reptilia]
-
A.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
B.
reclassifiedAs
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
C.
replacedClass
chosen
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
D.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
E.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 6:07 a.m.