Triple
T767986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital Object Identifier system |
E16216
|
entity |
| Predicate | prefixAssignedBy |
P19704
|
FINISHED |
| Object | registration agency |
—
|
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: registration agency | Statement: [Digital Object Identifier system, prefixAssignedBy, registration agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixAssignedBy Context triple: [Digital Object Identifier system, prefixAssignedBy, registration agency]
-
A.
assignedByAbbreviation
Indicates that an assignment or designation was made by an entity identified through a specific abbreviation.
-
B.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
C.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
D.
namedByLeader
Indicates that an entity has been given its name by a specific leader or person in authority.
-
E.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a7648a6c8190a9051a3d177ff7e2 |
completed | March 1, 2026, 8:53 p.m. |
Created at: March 1, 2026, 7:37 p.m.