Triple
T7557377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAVE PAWS radar site |
E178701
|
entity |
| Predicate | dataProvidedTo |
P75992
|
FINISHED |
| Object | missile warning centers |
—
|
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: missile warning centers | Statement: [PAVE PAWS radar site, dataProvidedTo, missile warning centers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProvidedTo Context triple: [PAVE PAWS radar site, dataProvidedTo, missile warning centers]
-
A.
providedInformationTo
chosen
Indicates that one entity has supplied or communicated information to another entity.
-
B.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
C.
dataSubject
Indicates that one entity is the individual to whom the personal data or information in question relates.
-
D.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
E.
providesReferenceDataFor
Indicates that one entity supplies authoritative or supporting data used as a reference basis for another entity’s operations, analysis, or decisions.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8db3d508190850ed41854d69838 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.