Triple
T18506658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altaba Inc. |
E452213
|
entity |
| Predicate | coreBusinessOrigin |
P19812
|
FINISHED |
| Object | Yahoo! Inc. core internet operations |
—
|
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: Yahoo! Inc. core internet operations | Statement: [Altaba Inc., coreBusinessOrigin, Yahoo! Inc. core internet operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreBusinessOrigin Context triple: [Altaba Inc., coreBusinessOrigin, Yahoo! Inc. core internet operations]
-
A.
businessOrigin
chosen
Indicates the place, source, or context from which a business or commercial entity originates or was established.
-
B.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
C.
stateOfBusiness
Indicates the current operational or financial condition or status of a business at a given point in time.
-
D.
primaryBusinessArea
Indicates the main field, sector, or domain in which an entity primarily conducts its business activities.
-
E.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334266708190b59aca3a2218c095 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.