Triple
T2621889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tree of Life |
E59026
|
entity |
| Predicate | hasBranchCarvings |
P42275
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tree of Life, hasBranchCarvings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchCarvings Context triple: [Tree of Life, hasBranchCarvings, yes]
-
A.
carvedInto
Indicates that one entity has been shaped, cut, or sculpted so that it takes the form or likeness of another entity.
-
B.
carvedBy
Indicates that one entity has been shaped, cut, or sculpted from a material by another entity through a carving process.
-
C.
hasRockCarvingsFrom
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
-
D.
hasBranchCanals
Indicates that an entity possesses or is connected to one or more subsidiary or secondary canals branching off from a main canal.
-
E.
hasResinCanals
Indicates that an entity possesses resin canals as anatomical or structural features.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abdac82b688190886a6ec2d6e2abc7 |
completed | March 7, 2026, 7:59 a.m. |
Created at: March 6, 2026, 9:50 p.m.