Triple
T15627379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moritz v. Commissioner |
E375715
|
entity |
| Predicate | partyStatusOfMoritz |
P54268
|
FINISHED |
| Object | unmarried man |
—
|
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: unmarried man | Statement: [Moritz v. Commissioner, partyStatusOfMoritz, unmarried man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyStatusOfMoritz Context triple: [Moritz v. Commissioner, partyStatusOfMoritz, unmarried man]
-
A.
partyStatusContext
Indicates the contextual status or role a party holds within a specific situation, event, or legal/transactional framework.
-
B.
germanyParticipationStatus
Indicates whether and how Germany is participating in a specified event, activity, or arrangement.
-
C.
participantStatus
chosen
Indicates the role, condition, or level of involvement that a participant has within a specific event, process, or relationship.
-
D.
sisterParty
Indicates that two political parties are formally affiliated or closely aligned as counterpart organizations, often in different regions or countries.
-
E.
factionStatus
Indicates the current state or condition of a faction in relation to a particular context, system, or other entities.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb4301881908c7157227fdf79b6 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.