Triple
T22557369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerope |
E557722
|
entity |
| Predicate | givenForPurpose |
P12882
|
FINISHED |
| Object | to be sold abroad |
—
|
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: to be sold abroad | Statement: [Aerope, givenForPurpose, to be sold abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givenForPurpose Context triple: [Aerope, givenForPurpose, to be sold abroad]
-
A.
governedForPurpose
Indicates that one entity exercises governance or control over another specifically to achieve a particular purpose or intended function.
-
B.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
C.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
givenFor
chosen
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.