Triple
T2660522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOSA |
E54714
|
entity |
| Predicate | resultOfAudit |
P9662
|
FINISHED |
| Object | IOSA registration |
—
|
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: IOSA registration | Statement: [IOSA, resultOfAudit, IOSA registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfAudit Context triple: [IOSA, resultOfAudit, IOSA registration]
-
A.
typeOfAudit
Indicates the specific category or kind of audit being performed or referenced in relation to an entity.
-
B.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
C.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
D.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
E.
regulatoryOutcome
chosen
Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.