Triple
T1462681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauli exclusion principle |
E31547
|
entity |
| Predicate | concernsProperty |
P11116
|
FINISHED |
| Object | 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: spin | Statement: [Pauli exclusion principle, concernsProperty, spin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsProperty Context triple: [Pauli exclusion principle, concernsProperty, spin]
-
A.
concernsLayer
Indicates that something is related or pertains specifically to a particular layer within a layered structure or system.
-
B.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
C.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
D.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
E.
narrativeConcern
Indicates a relationship where something is thematically or structurally focused on, revolves around, or is primarily about a particular narrative topic or issue.
- 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_69a4c5b6e36c81909c47b2f7e66f17d7 |
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.