Triple
T9287238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oromerycidae |
E223423
|
entity |
| Predicate | morphologicallySimilarTo |
P31789
|
FINISHED |
| Object | camel-like mammals |
—
|
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: camel-like mammals | Statement: [Oromerycidae, morphologicallySimilarTo, camel-like mammals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morphologicallySimilarTo Context triple: [Oromerycidae, morphologicallySimilarTo, camel-like mammals]
-
A.
hasPhonologicalSimilarityTo
Indicates that two linguistic elements share similar sound patterns or phonological features.
-
B.
hasGrammaticalSimilarityTo
Indicates that two linguistic elements share similar grammatical structure, form, or function.
-
C.
hasMorphologyDistinctFrom
Indicates that the morphology (form or structure) of one entity is different from that of another entity.
-
D.
hasLexicalSimilarityWith
Indicates that two linguistic items share a significant degree of similarity in form, structure, or wording.
-
E.
relatedMorphologicalFeature
chosen
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0861425c81909e3ab11e19cc2f65 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.