Triple
T34288583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houris |
E879812
|
entity |
| Predicate | interpretationRange |
P195867
|
FINISHED |
| Object | literal interpretation |
—
|
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: literal interpretation | Statement: [Houris, interpretationRange, literal interpretation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretationRange Context triple: [Houris, interpretationRange, literal interpretation]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
rangeDescription
Indicates the span or interval of values, positions, or extents over which something applies or is valid.
-
C.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
D.
introducedRange
Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
-
E.
configurationRange
Indicates the span or limits of values or settings that a configuration can take or is defined over.
- F. None of above. chosen
Provenance (4 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:57 a.m.