Triple
T4616899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO standards |
E100888
|
entity |
| Predicate | areDevelopedThrough |
P19846
|
FINISHED |
| Object | consensus process |
—
|
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: consensus process | Statement: [ISO standards, areDevelopedThrough, consensus process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areDevelopedThrough Context triple: [ISO standards, areDevelopedThrough, consensus process]
-
A.
developedThrough
chosen
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
B.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
D.
cultDeveloped
Indicates that a cult or devoted following has formed and grown around an entity, typically as a result of its influence, appeal, or impact.
-
E.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
- 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.