Triple
T3080270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Doty |
E64238
|
entity |
| Predicate | legalStatusAtArrival |
P45748
|
FINISHED |
| Object | indentured servant |
—
|
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: indentured servant | Statement: [Edward Doty, legalStatusAtArrival, indentured servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAtArrival Context triple: [Edward Doty, legalStatusAtArrival, indentured servant]
-
A.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
B.
residencyStatus
Indicates the legal or official residential classification of an entity within a particular jurisdiction or context.
-
C.
positionOnImmigration
Indicates a stance or viewpoint that an entity holds regarding immigration policies or issues.
-
D.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
E.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a9d61081909953eb2f4ad4537e |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.