Triple
T25114153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | au |
E629079
|
entity |
| Predicate | telecomStandardSupported |
P157657
|
FINISHED |
| Object | LTE |
—
|
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: LTE | Statement: [au, telecomStandardSupported, LTE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telecomStandardSupported Context triple: [au, telecomStandardSupported, LTE]
-
A.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
B.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
C.
telecomRegime
Indicates a regulatory or governance framework that defines how telecommunications services are organized, controlled, and operated within a given context.
-
D.
supportsGSM
Indicates that one entity provides compatibility with or operational support for GSM (Global System for Mobile communications) technology for another entity.
-
E.
supportsVoIP
Indicates that one entity provides the capability for Voice over IP (VoIP) communication to or for another entity.
- F. None of above. chosen
Provenance (4 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46579b7708190bc899259bf755f58 |
completed | May 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:27 a.m.