Triple
T22631702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP Core Network and Terminals (CT) |
E558569
|
entity |
| Predicate | hasWorkingGroup |
P1382
|
FINISHED |
| Object | CT4 |
—
|
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: CT4 | Statement: [3GPP Core Network and Terminals (CT), hasWorkingGroup, CT4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CT4 Context triple: [3GPP Core Network and Terminals (CT), hasWorkingGroup, CT4]
-
A.
CT4
chosen
CT4 is a 3GPP working group responsible for specifying protocols and interfaces for core network and terminal interoperability in mobile telecommunications systems.
-
B.
CT4
CT4 is a UK postcode district covering rural and suburban areas south of Canterbury in Kent, England.
-
C.
CT1
CT1 is a 3GPP working group responsible for specifying core network and terminal aspects of mobile telecommunications systems.
-
D.
CT1
CT1 is a central Canterbury postcode district in the CT area of southeast England, covering much of the historic city and its immediate surroundings.
-
E.
CT3
CT3 is a 3GPP Core Network and Terminals working group responsible for developing and maintaining signaling protocols and related specifications for mobile telecommunications networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17009ecb0819082f94505b0e2c5b8 |
completed | April 29, 2026, 2:42 a.m. |
Created at: April 17, 2026, 3:02 p.m.