Triple
T856988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chersina |
E18513
|
entity |
| Predicate | familyCommonName |
P570
|
FINISHED |
| Object | tortoises |
—
|
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: tortoises | Statement: [Chersina, familyCommonName, tortoises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyCommonName Context triple: [Chersina, familyCommonName, tortoises]
-
A.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
-
B.
familyNameCategory
Indicates that an entity is associated with a particular classification or grouping based on its family name.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
commonName
chosen
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
E.
hasLastNameInCommonWith
Indicates that two entities share the same last name.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4d47508190b48d944aa2d881bf |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.