Triple
T23989223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z39.96 |
E605017
|
entity |
| Predicate | approvedByAbbreviation |
P154526
|
FINISHED |
| Object | ANSI |
E6170
|
NE 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: ANSI | Statement: [Z39.96, approvedByAbbreviation, ANSI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedByAbbreviation Context triple: [Z39.96, approvedByAbbreviation, ANSI]
-
A.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
D.
approvalFor
Indicates that one entity grants or has granted permission or consent for another entity’s action, request, or status.
-
E.
approvalType
Indicates the specific category or kind of approval that has been granted or requested in the relationship between entities.
- F. None of above. chosen
Provenance (5 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38a40588190887c2abc6565bbf4 |
completed | April 29, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f7e8c93c4819081cbeccc5eca921c |
completed | May 21, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:37 p.m.