Triple
T25582469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFO |
E641286
|
entity |
| Predicate | fullNameOfOrganizationInSeries |
P44868
|
FINISHED |
| Object | Supreme Headquarters Alien Defence Organisation |
—
|
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: Supreme Headquarters Alien Defence Organisation | Statement: [UFO, fullNameOfOrganizationInSeries, Supreme Headquarters Alien Defence Organisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameOfOrganizationInSeries Context triple: [UFO, fullNameOfOrganizationInSeries, Supreme Headquarters Alien Defence Organisation]
-
A.
namedForOrganization
Indicates that one entity bears a name that is derived from or given in honor of a particular organization.
-
B.
organizerFullName
Indicates the full personal name of the entity that serves as the organizer of an event or activity.
-
C.
organizationName
Indicates that an entity has a specific official name as an organization.
-
D.
associatedOrganizationFullName
chosen
Indicates that an entity is linked to an organization by specifying the organization’s complete, official name.
-
E.
originalOrganizationName
Indicates the name by which an organization was originally known before any renaming or rebranding.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f93653948190baf191db01add4b2 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:13 p.m.