Triple
T27131534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCD |
E681573
|
entity |
| Predicate | isHighlyLiquid |
P25265
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MCD, isHighlyLiquid, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighlyLiquid Context triple: [MCD, isHighlyLiquid, true]
-
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.
isWidelyTraded
Indicates that an asset or item is frequently bought and sold across many participants or markets, resulting in high trading activity and liquidity.
-
C.
isDilutable
Indicates that a substance or solution can be thinned or reduced in concentration by adding another medium, typically a solvent.
-
D.
isWidelyHeld
Indicates that a belief, opinion, or view is shared by a large number of people or is broadly accepted within a group or population.
-
E.
liquidityScreening
Indicates that an entity is evaluated or filtered based on its ability to meet short-term financial obligations or convert assets to cash (i.e., its liquidity).
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6247832a48190b820e8c0c22ff5db |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:04 a.m.