Triple
T10158996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFnet |
E233840
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | EFnet |
E233840
|
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: EFnet | Statement: [EFnet, abbreviation, EFnet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EFnet Context triple: [EFnet, abbreviation, EFnet]
-
A.
EFnet
chosen
EFnet is one of the oldest and largest Internet Relay Chat (IRC) networks, known for its decentralized structure and influential role in early online chat culture.
-
B.
Undernet
Undernet is one of the largest and oldest Internet Relay Chat (IRC) networks, known for its extensive global user base and role in the early development of online chat communities.
-
C.
MILNET
MILNET was a U.S. military computer network that formed the unclassified, operational branch of the early Defense Data Network, separate from research-focused ARPANET.
-
D.
RFC 1459
RFC 1459 is the original specification that defines the core protocol, architecture, and message formats for the Internet Relay Chat (IRC) system.
-
E.
FFA
FFA is the commonly used abbreviation for the Fédération Française d’Athlétisme, the governing body for athletics in France.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d300b7b3108190a8e7581193c322be |
completed | April 6, 2026, 12:39 a.m. |
Created at: March 30, 2026, 9:09 p.m.