Triple
T8555638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11757 Fizeau |
E202556
|
entity |
| Predicate | namedForWorkOn |
P83605
|
FINISHED |
| Object | speed of light |
—
|
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: speed of light | Statement: [11757 Fizeau, namedForWorkOn, speed of light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForWorkOn Context triple: [11757 Fizeau, namedForWorkOn, speed of light]
-
A.
namedForWork
Indicates that one entity is named in honor of, or derived from the title of, a particular work (such as a book, film, artwork, or other creative production).
-
B.
givenForWorkIn
Indicates that something (such as payment, benefit, or item) is provided to an entity specifically in exchange for or in connection with work performed in a particular role, job, or context.
-
C.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
-
D.
namedForEmployer
Indicates that an entity is named after, or in honor of, its employer.
-
E.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
- F. None of above. chosen
Provenance (4 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe88bcce081909e12e4037a0e6323 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:19 p.m.