Triple
T5903349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy disk |
E131279
|
entity |
| Predicate | hasCentralIntensity |
P66832
|
FINISHED |
| Object | maximum at center |
—
|
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: maximum at center | Statement: [Airy disk, hasCentralIntensity, maximum at center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralIntensity Context triple: [Airy disk, hasCentralIntensity, maximum at center]
-
A.
hasCentralDensity
Indicates that an entity possesses a specified value for its density at the central or core region.
-
B.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
C.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
D.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
E.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 3:58 p.m.