Triple
T5389977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Administration Party |
E120296
|
entity |
| Predicate | ceasedToExistAs |
P35873
|
FINISHED |
| Object | distinct faction by mid-1790s |
—
|
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: distinct faction by mid-1790s | Statement: [Anti-Administration Party, ceasedToExistAs, distinct faction by mid-1790s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedToExistAs Context triple: [Anti-Administration Party, ceasedToExistAs, distinct faction by mid-1790s]
-
A.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
B.
existedAs
chosen
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
C.
ceasedActivityUnder
Indicates that an entity stopped performing a particular activity while under the authority, influence, or conditions imposed by another entity.
-
D.
ceasedOperationsAs
Indicates that an entity stopped functioning or operating in a particular role, capacity, or status.
-
E.
diedAs
Indicates that an entity ceased to live in a particular role, state, or identity.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8716ae9c8190a729222a8b9eb460 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.