Triple
T29580775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternity |
E753570
|
entity |
| Predicate | excludesFromReach |
P171816
|
FINISHED |
| Object | prehistory |
—
|
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: prehistory | Statement: [Eternity, excludesFromReach, prehistory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesFromReach Context triple: [Eternity, excludesFromReach, prehistory]
-
A.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
B.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
C.
isExcludedFor
Indicates that a particular entity is not allowed, applicable, or considered within a specified context, condition, or set.
-
D.
exemptedFrom
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
E.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 6:06 p.m.