Triple
T9897828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surface Go |
E182218
|
entity |
| Predicate | optionalConnectivity |
P36910
|
FINISHED |
| Object | LTE Advanced |
—
|
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: LTE Advanced | Statement: [Surface Go, optionalConnectivity, LTE Advanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionalConnectivity Context triple: [Surface Go, optionalConnectivity, LTE Advanced]
-
A.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
B.
connectivityFeatures
chosen
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
C.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
connectivityThreshold
Indicates the minimum level of connection or linkage required between entities for a specified relationship, interaction, or network condition to be considered established.
-
E.
improvesConnectivityBetween
Indicates that one entity enhances, strengthens, or facilitates the quality or efficiency of the connection or communication between two other entities.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ac27d88190b8255f7e616f95c9 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.