Triple
T29371622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMPS |
E744869
|
entity |
| Predicate | initialDeploymentCountry |
P89013
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [AMPS, initialDeploymentCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialDeploymentCountry Context triple: [AMPS, initialDeploymentCountry, United States]
-
A.
launchedInCountry
Indicates that an entity (such as a product, service, or mission) was officially initiated, introduced, or started within a specified country.
-
B.
registrationCountry
Indicates the country in which an entity is officially registered or incorporated.
-
C.
countryOfDeployment
chosen
Indicates the country where an entity (such as a person, unit, or asset) is currently or was assigned, stationed, or operating.
-
D.
countryOrRegionUsed
Indicates that something is used within, or applies to, a specific country or geographic region.
-
E.
signedInCountry
Indicates that an agreement, document, or contract was formally signed within a particular country.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 2:27 p.m.