Triple
T32119620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sciences religieuses |
E820330
|
entity |
| Predicate | usesMethodFrom |
P33646
|
FINISHED |
| Object | humanities |
—
|
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: humanities | Statement: [Sciences religieuses, usesMethodFrom, humanities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMethodFrom Context triple: [Sciences religieuses, usesMethodFrom, humanities]
-
A.
usesMethods
chosen
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
B.
implementsMethod
Indicates that one entity provides a concrete implementation of a specified method defined or required elsewhere.
-
C.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
D.
adoptedByMethod
Indicates that something is accepted, implemented, or brought into use through a specified method or procedure.
-
E.
usesAccessMethod
Indicates that one entity employs or relies on a particular access method to reach, interact with, or retrieve another entity or resource.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 12:28 a.m.