Triple
T19201714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son of the Tree That Owns Itself |
E470122
|
entity |
| Predicate | isVisitedFor |
P134945
|
FINISHED |
| Object | its unique ownership legend |
—
|
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: its unique ownership legend | Statement: [Son of the Tree That Owns Itself, isVisitedFor, its unique ownership legend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVisitedFor Context triple: [Son of the Tree That Owns Itself, isVisitedFor, its unique ownership legend]
-
A.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
-
B.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
C.
visitedDuring
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
D.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
E.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f9991ba48190ab92805daec3877b |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 12:07 p.m.