Triple
T36600568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APHINITY |
E902901
|
entity |
| Predicate | regionOfEnrollment |
P201823
|
FINISHED |
| Object | Europe |
—
|
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: Europe | Statement: [APHINITY, regionOfEnrollment, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfEnrollment Context triple: [APHINITY, regionOfEnrollment, Europe]
-
A.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
B.
traditionalRegionOfResidence
Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
-
C.
reportedRegion
Indicates that a specified region is the one referenced or identified in a report or reporting context.
-
D.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
E.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
| PDg | Predicate description generation | batch_6a00262cc9408190b95076a2d3da057d |
completed | May 10, 2026, 6:31 a.m. |
Created at: May 3, 2026, 4:11 p.m.