Triple
T37104561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapiro delay |
E918804
|
entity |
| Predicate | isMaximizedWhen |
P4228
|
FINISHED |
| Object | signal passes close to the massive body |
—
|
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: signal passes close to the massive body | Statement: [Shapiro delay, isMaximizedWhen, signal passes close to the massive body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaximizedWhen Context triple: [Shapiro delay, isMaximizedWhen, signal passes close to the massive body]
-
A.
maximizedUnder
Indicates that a quantity, value, or objective reaches its greatest possible level subject to specified conditions or constraints.
-
B.
launchedAsMax
Indicates that something was initiated, released, or started in its maximum or highest-capacity form.
-
C.
isMaximumWhen
chosen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
D.
windowManagementStyle
Indicates how windows are organized, displayed, and controlled within a user interface or system.
-
E.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.