Triple
T31943887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_tb |
E815594
|
entity |
| Predicate | isLargestElementIn |
P76336
|
FINISHED |
| Object | third row of CKM matrix |
—
|
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: third row of CKM matrix | Statement: [V_tb, isLargestElementIn, third row of CKM matrix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestElementIn Context triple: [V_tb, isLargestElementIn, third row of CKM matrix]
-
A.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
B.
isLargestTypeOf
Indicates that one entity represents the largest variant, category, or instance within a specified type or group relative to others.
-
C.
hasLargestElementOrder
chosen
Indicates that, among a set of elements (typically group elements), one element has an order that is greater than or equal to the order of every other element in the set.
-
D.
isLargestWithProperty
Indicates that an entity is the largest among a set of entities that share a specified property.
-
E.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:06 a.m.