Triple
T11058582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANA Group |
E261443
|
entity |
| Predicate | foundedAsGroupStructure |
P364
|
FINISHED |
| Object | ANA Holdings reorganization in 2013 |
—
|
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: ANA Holdings reorganization in 2013 | Statement: [ANA Group, foundedAsGroupStructure, ANA Holdings reorganization in 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsGroupStructure Context triple: [ANA Group, foundedAsGroupStructure, ANA Holdings reorganization in 2013]
-
A.
foundedAsGrouping
Indicates that an entity was originally established or created as part of a particular group, category, or organizational grouping.
-
B.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
foundedOrganization
Indicates that an entity established or created an organization.
-
D.
foundingMembersCollectiveName
Indicates the shared collective name used to refer to the group of founding members.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a2efa48190b290f43dfe836501 |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.