Triple
T23302400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP2 |
E590337
|
entity |
| Predicate | developsSpecificationFor |
P30412
|
FINISHED |
| Object | CDMA2000-based mobile systems |
—
|
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: CDMA2000-based mobile systems | Statement: [3GPP2, developsSpecificationFor, CDMA2000-based mobile systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsSpecificationFor Context triple: [3GPP2, developsSpecificationFor, CDMA2000-based mobile systems]
-
A.
developsComponentFor
Indicates that one entity creates or builds a component intended to be used by or within another entity.
-
B.
developsWhen
Indicates that one condition, feature, or state comes into existence or forms as a result of another condition, feature, or state.
-
C.
developmentFor
Indicates that one entity is created, adapted, or advanced specifically for the benefit, use, or purpose of another entity.
-
D.
developsStandardsFor
chosen
Indicates that one entity creates, defines, or establishes formal standards, guidelines, or specifications for another entity or domain.
-
E.
developsTechnologyFor
Indicates that one entity creates, improves, or engineers technology specifically intended to be used by or to benefit another entity.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972406a08190bbf355cc7a9f8432 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.