Triple
T17037624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acanthodii |
E413361
|
entity |
| Predicate | notCloselyRelatedTo |
P5202
|
FINISHED |
| Object | modern sharks |
—
|
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: modern sharks | Statement: [Acanthodii, notCloselyRelatedTo, modern sharks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notCloselyRelatedTo Context triple: [Acanthodii, notCloselyRelatedTo, modern sharks]
-
A.
notGeneticallyRelatedTo
Indicates that there is no genetic or hereditary relationship between the two entities.
-
B.
moreDistantlyRelatedTo
chosen
Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
-
C.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
D.
notStronglyAssociatedWith
Indicates that two entities have little to no meaningful or statistically significant relationship or connection with each other.
-
E.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f38b58819093af4054c3459726 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.