Triple
T24991824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tree of knowledge |
E625466
|
entity |
| Predicate | rootsSymbolize |
P89328
|
FINISHED |
| Object | fundamental principles |
—
|
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: fundamental principles | Statement: [Tree of knowledge, rootsSymbolize, fundamental principles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rootsSymbolize Context triple: [Tree of knowledge, rootsSymbolize, fundamental principles]
-
A.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
-
B.
reverseSymbolizes
Indicates that one entity serves as a symbolic representation of another, but in an inverse or opposite direction to the usual symbolism relationship.
-
C.
symbolizedIn
chosen
Indicates that one entity serves as a symbol or representation of another entity.
-
D.
mountSymbolizes
Indicates that a mount (such as a horse, vehicle, or rideable creature) serves as a symbolic representation of something else, such as status, role, or affiliation.
-
E.
routeSymbol
Indicates that a particular symbol or code is used to represent or identify a specific route.
- 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_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. |
Created at: April 18, 2026, 6:03 a.m.