Triple
T187487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMP |
E4013
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | ARPANET infrastructure |
E1032
|
NE 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 infrastructure | Statement: [IMP, partOf, ARPANET infrastructure]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ARPANET infrastructure Context triple: [IMP, partOf, ARPANET infrastructure]
-
A.
ARPANET
chosen
ARPANET was the pioneering packet-switching network developed in the late 1960s that became the technical foundation of the modern Internet.
-
B.
Internet Protocol
Internet Protocol is the core networking protocol that defines how data packets are addressed and routed across interconnected computer networks, forming the foundation of the modern internet.
-
C.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
D.
Defense Data Network
The Defense Data Network was a U.S. Department of Defense global computer network that succeeded ARPANET and supported secure military and government communications.
-
E.
OSI protocol suite
The OSI protocol suite is a conceptual networking framework that defines a seven-layer model for how different communication protocols interact to enable data exchange across networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a30cc6bfdc819091478e5102a3d64f |
completed | Feb. 28, 2026, 3:41 p.m. |
Created at: Feb. 28, 2026, 2:40 a.m.