Triple
T5796017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP100 |
E128509
|
entity |
| Predicate | liquidityFocus |
P25265
|
FINISHED |
| Object | highly traded U.S. stocks |
—
|
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: highly traded U.S. stocks | Statement: [SP100, liquidityFocus, highly traded U.S. stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liquidityFocus Context triple: [SP100, liquidityFocus, highly traded U.S. stocks]
-
A.
hasLiquidityCharacteristic
chosen
Indicates that one entity possesses or is associated with a particular liquidity-related property or feature in relation to another entity.
-
B.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
C.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
flowsMostly
Indicates that one entity predominantly flows or moves in the direction of, or through, another entity, more so than in other directions or paths.
-
E.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.