Triple
T27593504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marathon |
E699836
|
entity |
| Predicate | canScale |
P135871
|
FINISHED |
| Object | applications horizontally |
—
|
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: applications horizontally | Statement: [Marathon, canScale, applications horizontally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canScale Context triple: [Marathon, canScale, applications horizontally]
-
A.
isScalable
chosen
Indicates that something can handle increasing amounts of work, users, or data without a proportional loss of performance or efficiency.
-
B.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
-
C.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
D.
wasScaledFor
Indicates that something was adjusted in size, capacity, or extent to suit a particular context, requirement, or target.
-
E.
isScaleInvariant
Indicates that a property, equation, or system remains unchanged when all relevant dimensions or variables are uniformly scaled by a common factor.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63055b96c8190b53a73a68c05c133 |
completed | May 2, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.