Triple
T1463289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michelson interferometer |
E31561
|
entity |
| Predicate | typicalConfiguration |
P5084
|
FINISHED |
| Object | two perpendicular arms |
—
|
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: two perpendicular arms | Statement: [Michelson interferometer, typicalConfiguration, two perpendicular arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConfiguration Context triple: [Michelson interferometer, typicalConfiguration, two perpendicular arms]
-
A.
typicalDeployment
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
-
B.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.