Triple
T36870553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPST instanton |
E911211
|
entity |
| Predicate | fieldStrengthCondition |
P81799
|
FINISHED |
| Object | F = *F |
—
|
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: F = *F | Statement: [BPST instanton, fieldStrengthCondition, F = *F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldStrengthCondition Context triple: [BPST instanton, fieldStrengthCondition, F = *F]
-
A.
fieldStrengthProperty
Indicates a relationship where a field is characterized or quantified by a specific strength value or property.
-
B.
typicalFieldStrength
chosen
Indicates the usual or characteristic magnitude of a field (such as electric, magnetic, or other physical field) associated with an entity or situation.
-
C.
featsOfStrengthCondition
Indicates a condition under which feats of strength are performed, evaluated, or become applicable in a given context.
-
D.
fieldQuality
Indicates the assessed level or degree of quality associated with a particular field or attribute in a given context.
-
E.
fieldRestriction
Indicates that access to or use of a particular field, area, or domain is limited or constrained by specified rules or conditions.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.