Triple
T11098863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clebsch–Gordan coefficients |
E262449
|
entity |
| Predicate | canBeTabulated |
P2463
|
FINISHED |
| Object | finite tables for small j values |
—
|
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: finite tables for small j values | Statement: [Clebsch–Gordan coefficients, canBeTabulated, finite tables for small j values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTabulated Context triple: [Clebsch–Gordan coefficients, canBeTabulated, finite tables for small j values]
-
A.
isTabulatedBy
Indicates that data, values, or information are organized, arranged, or recorded in a table by a specified agent or process.
-
B.
canBe
chosen
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
C.
canBeDissectedBy
Indicates that one entity is capable of being divided or analyzed into parts by another entity or method.
-
D.
canBeViewedAs
Indicates that one entity may be interpreted, treated, or understood as another entity or type under some perspective or conditions.
-
E.
canBeEmbeddedIn
Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0c46308190889b94c23ebaca62 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.