Triple
T21192000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD-SCDMA |
E522232
|
entity |
| Predicate | usesFrameStructure |
P124922
|
FINISHED |
| Object | time slots |
—
|
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: time slots | Statement: [TD-SCDMA, usesFrameStructure, time slots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFrameStructure Context triple: [TD-SCDMA, usesFrameStructure, time slots]
-
A.
usesFrame
chosen
Indicates that one entity employs, relies on, or is structured around a particular frame, framework, or reference structure provided by another entity.
-
B.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
C.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
D.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
E.
supportsStructure
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.