Triple
T4165613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula of Universal Law |
E84437
|
entity |
| Predicate | exampleApplication |
P54441
|
FINISHED |
| Object | duty not to make false promises |
—
|
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: duty not to make false promises | Statement: [Formula of Universal Law, exampleApplication, duty not to make false promises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleApplication Context triple: [Formula of Universal Law, exampleApplication, duty not to make false promises]
-
A.
definesApplication
Indicates that one entity specifies or establishes the purpose, scope, or behavior of an application associated with another entity.
-
B.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
C.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
D.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
-
E.
applicationLocation
Indicates the place or environment where an application is deployed, used, or made available.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02ac8e788190a8f3563a2903bbad |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:44 p.m.