Triple
T1740566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FVEY |
E38222
|
entity |
| Predicate | usesNetwork |
P5033
|
FINISHED |
| Object | global signals intelligence network |
—
|
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: global signals intelligence network | Statement: [FVEY, usesNetwork, global signals intelligence network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNetwork Context triple: [FVEY, usesNetwork, global signals intelligence network]
-
A.
hasNetworkUS
Indicates that an entity possesses, operates, or is associated with a network located in or serving the United States.
-
B.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
operatesNetwork
chosen
Indicates that an entity manages, controls, or runs the functioning of a network.
-
E.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.