Triple
T1483884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway polynomial |
E29419
|
entity |
| Predicate | valueOnSplitUnion |
P21779
|
FINISHED |
| Object | for split union L₁ ⊔ L₂, ∇(L₁ ⊔ L₂) = 0 |
—
|
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: for split union L₁ ⊔ L₂, ∇(L₁ ⊔ L₂) = 0 | Statement: [Conway polynomial, valueOnSplitUnion, for split union L₁ ⊔ L₂, ∇(L₁ ⊔ L₂) = 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueOnSplitUnion Context triple: [Conway polynomial, valueOnSplitUnion, for split union L₁ ⊔ L₂, ∇(L₁ ⊔ L₂) = 0]
-
A.
inUnionFlagRepresents
Indicates that one entity is represented or symbolized by its inclusion on the union flag of another entity.
-
B.
hasUnionRepresentation
Indicates that an entity is represented by a labor union in negotiations or employment-related matters.
-
C.
effectOfUnion
chosen
Indicates the outcome or consequence that results from forming a union or combining entities.
-
D.
formedByUnionOf
Indicates that something is created or defined as the union or combination of multiple other things.
-
E.
introducedIntoUnionFlag
Indicates that an entity (such as a state or region) was formally admitted or incorporated into a union or larger political entity.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c679714c8190ac53630fb49e19c5 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.