Triple
T3850918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Fire Protection Association standards |
E85291
|
entity |
| Predicate | developmentProcess |
P41845
|
FINISHED |
| Object | consensus-based |
—
|
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-based | Statement: [National Fire Protection Association standards, developmentProcess, consensus-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentProcess Context triple: [National Fire Protection Association standards, developmentProcess, consensus-based]
-
A.
developmentMethod
chosen
Indicates the process, technique, or approach used to create, build, or evolve something.
-
B.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
C.
developmentFunction
Indicates a relationship where one entity serves as a function, role, or mechanism that drives, supports, or shapes the development or growth of another entity.
-
D.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
E.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.