Triple
T22423049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdős number concept |
E554296
|
entity |
| Predicate | hasBaseCase |
P148120
|
FINISHED |
| Object | Erdős number 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: Erdős number 0 | Statement: [Erdős number concept, hasBaseCase, Erdős number 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseCase Context triple: [Erdős number concept, hasBaseCase, Erdős number 0]
-
A.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
B.
hasBaseCount
Indicates the number of base units or fundamental components associated with an entity.
-
C.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
E.
hasBaseIndex
Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2af620819083338127e78137dc |
completed | April 29, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.