Triple
T2184776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemnian language |
E49124
|
entity |
| Predicate | hasUnclear |
P9778
|
FINISHED |
| Object | phonology |
—
|
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: phonology | Statement: [Lemnian language, hasUnclear, phonology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnclear Context triple: [Lemnian language, hasUnclear, phonology]
-
A.
hasUncertainty
chosen
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
B.
hasUnknown
Indicates that an entity possesses or is associated with information, attributes, or values that are not known or not specified.
-
C.
hasUncertainBoundary
Indicates that the boundary or extent of something is not clearly defined, fixed, or precisely known.
-
D.
languageAmbiguity
Indicates that the meaning, interpretation, or reference of a linguistic expression is unclear or can be understood in multiple ways.
-
E.
hasUncertainHistoricBasis
Indicates that the historical foundation or authenticity of the related fact, event, or relationship is doubtful, disputed, or not firmly established.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.