Triple
T22194951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HRLT |
E548521
|
entity |
| Predicate | mayExistIn |
P51053
|
FINISHED |
| Object | international organizations |
—
|
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: international organizations | Statement: [HRLT, mayExistIn, international organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayExistIn Context triple: [HRLT, mayExistIn, international organizations]
-
A.
canExistAt
chosen
Indicates that an entity is capable of being present or occurring at a specified location, time, or context.
-
B.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
C.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
D.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
E.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae622ac8190b4fc9e6e4ccd0726 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.