Triple
T6714347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Canas |
E153225
|
entity |
| Predicate | involvedInField |
P3
|
FINISHED |
| Object | immigration law |
—
|
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: immigration law | Statement: [De Canas, involvedInField, immigration law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedInField Context triple: [De Canas, involvedInField, immigration law]
-
A.
developedInField
Indicates that an entity (such as a method, theory, or technology) was created, formulated, or advanced within a particular academic or professional field.
-
B.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
E.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d122d6cc81909bde0c94fb95f016 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.