Triple
T4616756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO High Level Structure |
E100885
|
entity |
| Predicate | hasTargetUser |
P6943
|
FINISHED |
| Object | standards developers |
—
|
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: standards developers | Statement: [ISO High Level Structure, hasTargetUser, standards developers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetUser Context triple: [ISO High Level Structure, hasTargetUser, standards developers]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
hasUser
chosen
Indicates that an entity is associated with or linked to a specific user.
-
C.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
hasTargetIssue
Indicates that an entity is associated with or directed toward a specific issue, problem, or concern as its focus.
-
E.
hasUserService
Indicates that an entity is associated with or utilizes a particular user-related service.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.