Triple
T29107862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniParc |
E736814
|
entity |
| Predicate | assignsIdentifier |
P3732
|
FINISHED |
| Object | UPI |
—
|
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: UPI | Statement: [UniParc, assignsIdentifier, UPI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignsIdentifier Context triple: [UniParc, assignsIdentifier, UPI]
-
A.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
mayBeAssignedBy
Indicates that an entity has the potential or permission to be assigned by another entity, without asserting that the assignment has actually occurred.
-
C.
requiresAssignment
Indicates that one entity depends on another entity being assigned or allocated before it can proceed, function, or be considered valid.
-
D.
assignedByAbbreviation
Indicates that an assignment or designation was made by an entity identified through a specific abbreviation.
-
E.
haveIdentifier
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:16 a.m.