Triple
T10869151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Holy Sage and First Teacher |
E256605
|
entity |
| Predicate | impliesAttribute |
P96160
|
FINISHED |
| Object | supreme wisdom |
—
|
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: supreme wisdom | Statement: [Most Holy Sage and First Teacher, impliesAttribute, supreme wisdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesAttribute Context triple: [Most Holy Sage and First Teacher, impliesAttribute, supreme wisdom]
-
A.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
B.
impliesRole
Indicates that one role logically entails or gives rise to another role within a given context or system.
-
C.
impliesStatus
Indicates that one condition, fact, or state logically leads to or determines another status or outcome.
-
D.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
E.
conveysAttribute
Indicates that one entity communicates, expresses, or imparts a particular attribute or quality to another entity.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75170665881909944f92c2cdbe7e6 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.