Triple
T12892587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Functional Requirements for Bibliographic Records |
E308404
|
entity |
| Predicate | definesUserTask |
P67335
|
FINISHED |
| Object | find |
—
|
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: find | Statement: [Functional Requirements for Bibliographic Records, definesUserTask, find]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesUserTask Context triple: [Functional Requirements for Bibliographic Records, definesUserTask, find]
-
A.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
B.
definesTasksOf
chosen
Indicates that one entity specifies or establishes the tasks, duties, or responsibilities assigned to another entity.
-
C.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
D.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
E.
setTaskFor
Indicates assigning or configuring a specific task to be carried out for a particular entity or context.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971484aa08190a8adfafabe600903 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.