Triple
T4786532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tree That Owns Itself |
E106491
|
entity |
| Predicate | successorPlanted |
P58417
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Tree That Owns Itself, successorPlanted, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorPlanted Context triple: [Tree That Owns Itself, successorPlanted, 1942]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorReceives
Indicates that a successor entity obtains or is granted something (such as rights, assets, or responsibilities) from a predecessor.
-
C.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
D.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
E.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65d8f9d881909c24340b8dc6a104 |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.