Triple
T31347258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High-Wire Bicycle |
E799480
|
entity |
| Predicate | demonstratesConcept |
P463
|
FINISHED |
| Object | center of gravity |
—
|
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: center of gravity | Statement: [High-Wire Bicycle, demonstratesConcept, center of gravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstratesConcept Context triple: [High-Wire Bicycle, demonstratesConcept, center of gravity]
-
A.
demonstratedConcept
chosen
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
B.
designedToDemonstrate
Indicates that something was intentionally created or arranged for the purpose of showing, illustrating, or proving a particular concept, feature, or behavior.
-
C.
demonstratesTo
Indicates that one entity actively shows, explains, or proves something to another entity.
-
D.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
E.
demonstratedOn
Indicates that an action, behavior, or property is shown, illustrated, or proven using a particular entity as the example or subject.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f19a79c81909647d8eef6706e44 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.