Triple
T27812125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperoartia |
E702543
|
entity |
| Predicate | isMorePrimitiveThan |
P74057
|
FINISHED |
| Object | Gnathostomata |
—
|
NE NERFINISHED |
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: Gnathostomata | Statement: [Hyperoartia, isMorePrimitiveThan, Gnathostomata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMorePrimitiveThan Context triple: [Hyperoartia, isMorePrimitiveThan, Gnathostomata]
-
A.
hasPrimitive
Indicates that an entity is composed of, defined by, or associated with one or more basic, indivisible components or elements.
-
B.
isMoreSpecificThan
Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
-
C.
usesPrimitiveType
Indicates that one entity employs or relies on a specified primitive data type in its definition or implementation.
-
D.
isShallowComparedTo
Indicates that one entity has less depth or is less profound than another entity when compared.
-
E.
isCoarserThan
chosen
Indicates that one entity has a lower level of detail or granularity than another, representing a broader or less refined characterization or partition.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638683c9481908972dd3fdea5f389 |
completed | May 2, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:43 p.m.