Triple
T16266852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi ben Gershom |
E394896
|
entity |
| Predicate | madeContributionTo |
P30146
|
FINISHED |
| Object | trigonometry |
—
|
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: trigonometry | Statement: [Levi ben Gershom, madeContributionTo, trigonometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeContributionTo Context triple: [Levi ben Gershom, madeContributionTo, trigonometry]
-
A.
hasContributionFrom
chosen
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
-
C.
tributeFrom
Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
-
D.
missionContribution
Indicates that an entity plays a role in supporting, advancing, or fulfilling the mission or overarching purpose of another entity or organization.
-
E.
contributionBased
Indicates that something is determined, allocated, or structured according to the level or amount of contributions made by the involved entities.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.