Triple
T10807494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | graviton (hypothetical) |
E255005
|
entity |
| Predicate | mediatesForce |
P52163
|
FINISHED |
| Object | 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: gravity | Statement: [graviton (hypothetical), mediatesForce, gravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediatesForce Context triple: [graviton (hypothetical), mediatesForce, gravity]
-
A.
mediatedIn
Indicates that an entity acted as an intermediary or facilitator in bringing about, enabling, or influencing another entity or event.
-
B.
mediatedBetween
Indicates that an entity acted as an intermediary or go-between facilitating interaction, communication, or negotiation between two other entities.
-
C.
mediatesProcess
Indicates that an entity serves as an intermediary or conduit through which a process occurs, is carried out, or is regulated.
-
D.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
E.
associatedForce
chosen
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733b506488190921e6a1f4168dd9e |
completed | April 9, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.