Triple
T33156122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3771 |
E848578
|
entity |
| Predicate | standardsOrganization |
P49412
|
FINISHED |
| Object | Internet Society |
—
|
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: Internet Society | Statement: [RFC 3771, standardsOrganization, Internet Society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardsOrganization Context triple: [RFC 3771, standardsOrganization, Internet Society]
-
A.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
B.
standardOrganization
chosen
Indicates that an entity is an organization responsible for developing, maintaining, or endorsing standards.
-
C.
alliedStandardization
Indicates that entities collaborate to harmonize or unify standards, rules, or specifications.
-
D.
countryOfStandardization
Indicates that a given standard, specification, or norm is officially established, adopted, or primarily recognized within a particular country.
-
E.
standardsType
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:28 a.m.