Triple
T5451814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Split View multitasking |
E122386
|
entity |
| Predicate | ratioExample |
P55017
|
FINISHED |
| Object | 50-50 split |
—
|
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: 50-50 split | Statement: [Split View multitasking, ratioExample, 50-50 split]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratioExample Context triple: [Split View multitasking, ratioExample, 50-50 split]
-
A.
divisionExample
chosen
Indicates an example that illustrates or demonstrates a particular division or partitioning of something.
-
B.
relatedDivide
Indicates that one entity divides or partitions another entity in a way that is contextually or relationally significant, rather than purely numerical.
-
C.
isProportionalTo
Indicates that one quantity varies in constant ratio to another, so when one changes, the other changes by a fixed multiplicative factor.
-
D.
ratioToGold
Indicates the proportional relationship between a given quantity and a corresponding amount of gold.
-
E.
inverselyProportionalTo
Indicates that as the value of one quantity increases, the value of the other quantity decreases in such a way that their product remains constant.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.