Triple
T28880709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasComponentSpinConstraint |
P201491
|
FINISHED |
| Object | low effective spin |
—
|
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: low effective spin | Statement: [GW170814, hasComponentSpinConstraint, low effective spin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentSpinConstraint Context triple: [GW170814, hasComponentSpinConstraint, low effective spin]
-
A.
hasUnstableSpinAxis
Indicates that an entity’s axis of rotation is not steady over time, but instead wobbles or changes unpredictably.
-
B.
hasSpin
Indicates that one entity possesses or exhibits rotational motion or angular momentum.
-
C.
hasTypicalSpinState
Indicates the usual or characteristic spin quantum state that an entity (such as a particle or system) most commonly exhibits under normal conditions.
-
D.
hasSpatialComponent
Indicates that one entity includes, consists of, or is associated with another entity that represents a spatial part, region, or aspect of it.
-
E.
hasRotationalVelocity
Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: April 28, 2026, 7:43 a.m.