Triple
T2783286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three-Fifths Compromise |
E61746
|
entity |
| Predicate | textualPhrase |
P9883
|
FINISHED |
| Object | three fifths of all other Persons |
—
|
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: three fifths of all other Persons | Statement: [Three-Fifths Compromise, textualPhrase, three fifths of all other Persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualPhrase Context triple: [Three-Fifths Compromise, textualPhrase, three fifths of all other Persons]
-
A.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
B.
textFragment
chosen
Indicates that one piece of text is a constituent part or segment of a larger text.
-
C.
titlePhrase
Indicates that one entity is a phrase functioning as the title or name of another entity.
-
D.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
E.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdd00b65c8190a8ea444308c4fa2b |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.