Triple
T28880705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasNetworkSignificance |
P195443
|
FINISHED |
| Object | >5 sigma |
—
|
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: >5 sigma | Statement: [GW170814, hasNetworkSignificance, >5 sigma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkSignificance Context triple: [GW170814, hasNetworkSignificance, >5 sigma]
-
A.
hasCallSignificance
Indicates that a particular call or communication event holds special importance, priority, or relevance within a given context or process.
-
B.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
-
C.
hasTransportSignificance
Indicates that something plays an important role or has notable relevance within a transportation or transit context.
-
D.
hasCurrentSignificance
Indicates that something presently holds importance, relevance, or meaningful impact in the current context or time.
-
E.
hasNotableNetwork
Indicates that one entity is recognized for having a significant, influential, or widely connected network or set of relationships with other entities.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: April 28, 2026, 7:43 a.m.