Triple
T24991825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tree of knowledge |
E625466
|
entity |
| Predicate | trunkSymbolizes |
P157519
|
FINISHED |
| Object | core sciences or philosophy |
—
|
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: core sciences or philosophy | Statement: [Tree of knowledge, trunkSymbolizes, core sciences or philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trunkSymbolizes Context triple: [Tree of knowledge, trunkSymbolizes, core sciences or philosophy]
-
A.
trunkCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a trunk (such as that of a tree or similar object).
-
B.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
-
C.
trunkSegments
Indicates that an object is composed of or associated with specific segments of a trunk (such as a tree trunk or similar elongated main structure).
-
D.
trunkPrefix
Indicates that one entity serves as the initial, leading segment or prefix of another entity, often in a hierarchical or concatenated structure.
-
E.
trunkVolume
Indicates the volume or capacity of an entity’s trunk or main storage compartment.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a4639e8819090ce27c835eec2f0 |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:03 a.m.