Triple
T25354091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Growler program |
E635771
|
entity |
| Predicate | alliedExportPotential |
P158231
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [Growler program, alliedExportPotential, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedExportPotential Context triple: [Growler program, alliedExportPotential, Australia]
-
A.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
-
B.
energyExportDestination
Indicates the location or entity to which energy produced in one place is exported.
-
C.
majorExportersInclude
Indicates that a specified set of entities is among the primary exporters of a particular good, service, or resource.
-
D.
alliedEquivalents
Indicates that two or more entities are considered equivalent or interchangeable within the context of an alliance or cooperative relationship.
-
E.
alliedWithBasedOn
Indicates a relationship where two or more entities are allied with each other specifically due to, or grounded in, a particular basis, condition, or shared factor.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49dfedae88190a02f10196ef45ffa |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:34 p.m.