Triple
T10047474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule XV |
E207652
|
entity |
| Predicate | mainWorkContext |
P26453
|
FINISHED |
| Object | method of attaining certain knowledge |
—
|
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: method of attaining certain knowledge | Statement: [Rule XV, mainWorkContext, method of attaining certain knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkContext Context triple: [Rule XV, mainWorkContext, method of attaining certain knowledge]
-
A.
primaryWorkContext
Indicates the main environment, setting, or domain in which an entity typically performs its work or primary activities.
-
B.
mainWorkSite
Indicates the primary location or site where an entity mainly performs its work or operations.
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
hasWorkContext
chosen
Indicates that an entity is associated with a particular work-related situation, environment, or context in which it is relevant or applies.
-
E.
mainWorkInterpreted
Indicates that one work serves as the primary interpretation, translation, or explanatory rendering of another work.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf664dd881908786fcd802bf10da |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.