Triple
T7931752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Taara |
E184203
|
entity |
| Predicate | connectivityType |
P3937
|
FINISHED |
| Object | wireless backhaul |
—
|
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: wireless backhaul | Statement: [Project Taara, connectivityType, wireless backhaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectivityType Context triple: [Project Taara, connectivityType, wireless backhaul]
-
A.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
B.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
D.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
E.
connectorType
Indicates the specific kind or category of connection interface that links two 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ace87f081908635769942645e78 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.