Triple
T28622037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action |
E724408
|
entity |
| Predicate | canIncludeTerm |
P2920
|
FINISHED |
| Object | antisymmetric B-field coupling ∫ B_{μν}(X) ∂X^μ ∂X^ν |
—
|
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: antisymmetric B-field coupling ∫ B_{μν}(X) ∂X^μ ∂X^ν | Statement: [Polyakov action, canIncludeTerm, antisymmetric B-field coupling ∫ B_{μν}(X) ∂X^μ ∂X^ν]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIncludeTerm
Context triple: [Polyakov action, canIncludeTerm, antisymmetric B-field coupling ∫ B_{μν}(X) ∂X^μ ∂X^ν]
-
A.
hasTerm
chosen
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
B.
allowsIndexInclusion
Indicates that one entity permits another entity to be included or listed within an index or indexing system.
-
C.
canonicalSetIncludes
Indicates that a canonical or standard set contains the referenced element as one of its members.
-
D.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
E.
hasCustomTerm
Indicates that an entity is associated with a user-defined or non-standard term specific to a particular context or configuration.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:34 a.m.