Triple
T23871063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C. Bao |
E592728
|
entity |
| Predicate | standardizationBodyContext |
P1251
|
FINISHED |
| Object | IETF |
—
|
NE NERFINISHED |
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: IETF | Statement: [C. Bao, standardizationBodyContext, IETF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationBodyContext Context triple: [C. Bao, standardizationBodyContext, IETF]
-
A.
standardizationContext
Indicates the context, framework, or setting within which a standardization process or activity is defined or applied.
-
B.
hasStandardizationBody
chosen
Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
-
C.
standardizationScope
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
D.
standardizationStream
Indicates a process or pathway through which something is standardized or brought into conformity with a common standard.
-
E.
standardBody
Indicates that an entity conforms to a recognized or officially accepted body type, form, or physical specification.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfe1f948190ad2c0d5bbe0c7240 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.