Triple
T26523556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE Capital |
E670624
|
entity |
| Predicate | peakAssets |
P160605
|
FINISHED |
| Object | over US$500 billion |
—
|
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: over US$500 billion | Statement: [GE Capital, peakAssets, over US$500 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakAssets Context triple: [GE Capital, peakAssets, over US$500 billion]
-
A.
tracksAsset
Indicates that one entity monitors, records, or follows the status, location, or changes of another entity designated as an asset.
-
B.
primaryAsset
Indicates that one entity is the main or most important asset associated with another entity.
-
C.
asset
Indicates that one entity is a valuable resource, item, or property owned, controlled, or beneficially used by another entity.
-
D.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
E.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c430148190b0c42d341d5bde09 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:30 a.m.