Triple
T617227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cephalochordata |
E14432
|
entity |
| Predicate | hasDistinctHead |
P16674
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Cephalochordata, hasDistinctHead, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctHead Context triple: [Cephalochordata, hasDistinctHead, false]
-
A.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
-
B.
hasDistinctGrammar
Indicates that the subject’s grammar system is different in structure or rules from that of the object.
-
C.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
D.
hasDistinctCharacterSet
Indicates that two compared items use different sets of characters, with no character set being a subset or duplicate of the other.
-
E.
hasHeadCount
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49d76062c819083ac33f1f87097c7 |
completed | March 1, 2026, 8:11 p.m. |
Created at: March 1, 2026, 7:35 p.m.