Triple
T22604631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code Division Multiple Access |
E566521
|
entity |
| Predicate | multipleAccessComparison |
P116109
|
FINISHED |
| Object | alternative to TDMA |
—
|
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: alternative to TDMA | Statement: [Code Division Multiple Access, multipleAccessComparison, alternative to TDMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleAccessComparison Context triple: [Code Division Multiple Access, multipleAccessComparison, alternative to TDMA]
-
A.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
-
B.
accessComparedTo
chosen
Indicates how the level, ease, or quality of access to something compares between two entities or contexts.
-
C.
hasComparison
Indicates that one entity is being evaluated or contrasted relative to another entity based on some shared attribute or criterion.
-
D.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
E.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f162709d808190af83837104a190f9 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:52 p.m.