Triple
T7928145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6856 |
E184118
|
entity |
| Predicate | documentSeries |
P23871
|
FINISHED |
| Object | STD |
E184135
|
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: STD | Statement: [RFC 6856, documentSeries, STD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD Context triple: [RFC 6856, documentSeries, STD]
-
A.
ST
ST is the commonly used abbreviation for SkyTeam, a major global airline alliance.
-
B.
ST
ST is the two-letter ISO 3166-1 alpha-2 country code representing São Tomé and Príncipe.
-
C.
ST
ST is the common abbreviation for Stade Toulousain, a leading French rugby union club based in Toulouse.
-
D.
ST
ST is the common abbreviation for Sound Transit, the regional public transit agency serving the Seattle metropolitan area in Washington State.
-
E.
STD 1
chosen
STD 1 is an early Internet Standard that specifies the foundational Internet Protocol (IP), defining how data packets are addressed and routed across interconnected 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5bfd08e88190bc6b2d77a148ae57 |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:07 p.m.