Triple
T19941272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiotaurus |
E479312
|
entity |
| Predicate | rarityInSources |
P7075
|
FINISHED |
| Object | rarely mentioned in surviving ancient texts |
—
|
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: rarely mentioned in surviving ancient texts | Statement: [Ophiotaurus, rarityInSources, rarely mentioned in surviving ancient texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rarityInSources Context triple: [Ophiotaurus, rarityInSources, rarely mentioned in surviving ancient texts]
-
A.
rarity
chosen
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
rarityReason
Indicates the underlying cause or justification for why something is considered rare.
-
C.
instrumentRarity
Indicates how uncommon or scarce an instrument is relative to others.
-
D.
isRareTypeOf
Indicates that one entity is an uncommon or infrequently occurring subtype or category of another entity.
-
E.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6318848190a1dd3e0a6fea3fe2 |
completed | April 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.