Triple
T13451744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tree at the Furthest Limit |
E320622
|
entity |
| Predicate | beyondIt |
P20815
|
FINISHED |
| Object | only God |
—
|
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: only God | Statement: [Tree at the Furthest Limit, beyondIt, only God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beyondIt Context triple: [Tree at the Furthest Limit, beyondIt, only God]
-
A.
beyond
Indicates that one entity is located or extends farther than, or outside the limits or scope of, another reference point or boundary.
-
B.
extendsBeyond
Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
-
C.
liesBeyond
chosen
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
-
D.
usedBeyond
Indicates that something is utilized or applied in a scope, context, or manner that extends past its original, intended, or primary use.
-
E.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.