Triple
T6939056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomson cross section |
E160626
|
entity |
| Predicate | isotropic |
P14262
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thomson cross section, isotropic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isotropic Context triple: [Thomson cross section, isotropic, true]
-
A.
isIsotropic
chosen
Indicates that a property or behavior is identical in all directions, showing no directional dependence.
-
B.
is
Indicates that two entities are equivalent, share an attribute, or stand in a specified state or relation to each other.
-
C.
arity
Indicates the number of arguments or participants that a relation or function takes.
-
D.
asymmetric
Indicates that the relationship between two entities never holds in both directions simultaneously, so if it holds from A to B it cannot also hold from B to A.
-
E.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.