Triple
T37825395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Clarke |
E943043
|
entity |
| Predicate | legalSystemOverseen |
P201674
|
FINISHED |
| Object | colonial law of New York |
—
|
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: colonial law of New York | Statement: [George Clarke, legalSystemOverseen, colonial law of New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalSystemOverseen Context triple: [George Clarke, legalSystemOverseen, colonial law of New York]
-
A.
legalSystem
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
B.
legalSystemWorkedOn
Indicates that a legal system has been applied to, influenced, or modified by some agent or process.
-
C.
legalSystemWorkedIn
Indicates that a person carried out their professional legal activities within a particular legal system or jurisdiction.
-
D.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
-
E.
legalSystemImposed
Indicates that one authority or group has established and enforced a particular legal system upon another population or territory.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
| PDg | Predicate description generation | batch_6a00119ca1d881909a72a9c3b937c43c |
completed | May 10, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:19 p.m.