Triple
T2173778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London penetration depth |
E48480
|
entity |
| Predicate | canBeMeasuredBy |
P24236
|
FINISHED |
| Object | muon spin rotation |
—
|
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: muon spin rotation | Statement: [London penetration depth, canBeMeasuredBy, muon spin rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMeasuredBy Context triple: [London penetration depth, canBeMeasuredBy, muon spin rotation]
-
A.
measuredBy
chosen
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
-
B.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
C.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
D.
measuredProperty
Indicates that the subject is a measurement that quantifies or assesses the specified property of an entity.
-
E.
usesMetric
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.