Triple
T9184292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Martin |
E220414
|
entity |
| Predicate | legalStatusPursued |
P75705
|
FINISHED |
| Object | recognition as a human being |
—
|
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: recognition as a human being | Statement: [Andrew Martin, legalStatusPursued, recognition as a human being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusPursued Context triple: [Andrew Martin, legalStatusPursued, recognition as a human being]
-
A.
legalStatusAtIssue
chosen
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
B.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
C.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
hasLegalProceeding
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
E.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31734908190b8ebe3b57849ca5f |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.