Triple
T1483814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway groups |
E29418
|
entity |
| Predicate | hasCardinality |
P23694
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Conway groups, hasCardinality, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardinality Context triple: [Conway groups, hasCardinality, 3]
-
A.
cardinality
chosen
Indicates the number of distinct elements or members in a given set or collection.
-
B.
meetsAtLeast
Indicates that one entity encounters or comes into contact with another entity at least a specified minimum number of times or to a minimum required degree.
-
C.
hasMemberCountType
Indicates the type or classification used to describe how the number of members in a group or collection is represented.
-
D.
hasQualifier
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
-
E.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
- 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.