Triple
T35653392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFC |
E1030214
|
entity |
| Predicate | wasTradedDuring |
P155628
|
FINISHED |
| Object | U.S. housing bubble |
—
|
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: U.S. housing bubble | Statement: [CFC, wasTradedDuring, U.S. housing bubble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTradedDuring Context triple: [CFC, wasTradedDuring, U.S. housing bubble]
-
A.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
B.
tradedUsing
Indicates that an exchange or trade was conducted by means of a specified instrument, medium, or mechanism.
-
C.
isTradableDuring
chosen
Indicates that something can be legally or practically traded within a specified time period or during a particular event or condition.
-
D.
isTradedLike
Indicates that one entity is exchanged, valued, or handled in markets in a manner similar to another entity.
-
E.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f75dd908190936dd6260f6d6630 |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.