Triple
T31648827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neocyema erythrosoma |
E807660
|
entity |
| Predicate | hasCommonFeaturesWith |
P101792
|
FINISHED |
| Object | gulpers and pelican eels |
—
|
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: gulpers and pelican eels | Statement: [Neocyema erythrosoma, hasCommonFeaturesWith, gulpers and pelican eels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonFeaturesWith Context triple: [Neocyema erythrosoma, hasCommonFeaturesWith, gulpers and pelican eels]
-
A.
hasCommonTraitWith
chosen
Indicates that two entities share at least one trait, characteristic, or property in common.
-
B.
includesCommon
Indicates that two or more entities share at least one common element, component, or member within their respective sets or collections.
-
C.
hasCommonElement
Indicates that two sets, collections, or groups share at least one element in common.
-
D.
hasDialectalFeaturesSharedWith
Indicates that two language varieties share specific dialectal features or characteristics in common.
-
E.
hasCommonSpace
Indicates that two or more entities share access to the same physical or virtual area intended for joint or overlapping use.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a030425fa1c81908748583513552d2b |
completed | May 12, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0303ced28081908588b8a14c23efe9 |
completed | May 12, 2026, 10:41 a.m. |
Created at: April 30, 2026, 10:52 p.m.