Triple
T25263877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Hundred Southerners |
E633377
|
entity |
| Predicate | numberAssociation |
P177278
|
FINISHED |
| Object | 400 |
—
|
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: 400 | Statement: [Four Hundred Southerners, numberAssociation, 400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberAssociation Context triple: [Four Hundred Southerners, numberAssociation, 400]
-
A.
phraseAssociation
Indicates an associative relationship where one phrase is linked, connected, or contextually related to another phrase.
-
B.
positionAssociatedWith
Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
-
C.
numberDescribedAs
Indicates that a number is characterized, labeled, or referred to using a particular description or phrase.
-
D.
numberOfAssociationsRepresented
Indicates the total count of associations that are captured or represented by a given entity or construct.
-
E.
keyAssociation
Indicates an associative relationship where one entity serves as a key used to identify, access, or link to another entity or set of entities.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 21, 2026, 1:14 p.m.