Triple
T6561401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodman–Martínez–Thompson correlation |
E153789
|
entity |
| Predicate | hasVariantConstant |
P71817
|
FINISHED |
| Object | 584285 |
—
|
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: 584285 | Statement: [Goodman–Martínez–Thompson correlation, hasVariantConstant, 584285]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantConstant Context triple: [Goodman–Martínez–Thompson correlation, hasVariantConstant, 584285]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
-
C.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
D.
includesConstant
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
E.
hasVariantFamily
Indicates that one entity is related to another as a different version, type, or family variant of it.
- F. None of above. chosen
Provenance (4 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c1b007148190b5164d6d09584cdf |
completed | March 27, 2026, 5:43 p.m. |
Created at: March 27, 2026, 1:52 p.m.