Triple
T19846011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scientia est potentia |
E476860
|
entity |
| Predicate | complementTerm |
P162
|
FINISHED |
| Object | potentia |
—
|
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: potentia | Statement: [Scientia est potentia, complementTerm, potentia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complementTerm Context triple: [Scientia est potentia, complementTerm, potentia]
-
A.
complement
Indicates that one entity completes, enhances, or makes another entity whole or more effective by providing what it lacks.
-
B.
complements
chosen
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
C.
relatesComplementTo
Indicates that one entity serves as a complement or completing counterpart to another entity within a specified context or structure.
-
D.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
E.
successorOrComplement
Indicates that one entity either directly follows another in a sequence or serves as its logical or functional complement.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658091c608190b4eb9bcedd88e147 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.