Triple
T209165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCP |
E4675
|
entity |
| Predicate | standardizedOn |
P7508
|
FINISHED |
| Object | ARPANET hosts prior to 1983 |
—
|
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: ARPANET hosts prior to 1983 | Statement: [NCP, standardizedOn, ARPANET hosts prior to 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedOn Context triple: [NCP, standardizedOn, ARPANET hosts prior to 1983]
-
A.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
B.
standardizedIn
chosen
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
C.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
-
D.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
E.
standardizationInfluence
Indicates the extent to which one entity’s standards, norms, or standardization efforts shape, guide, or constrain another entity’s practices, processes, or specifications.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e8b9b908190b69a3f0594b95f7e |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b4e3c2881908d83e8218aa9f2d9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.