Triple
T38148732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutherford clan |
E952691
|
entity |
| Predicate | borderLawStatus |
P201852
|
FINISHED |
| Object | notorious reivers |
—
|
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: notorious reivers | Statement: [Rutherford clan, borderLawStatus, notorious reivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLawStatus Context triple: [Rutherford clan, borderLawStatus, notorious reivers]
-
A.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
B.
legalStatusAtArrival
Indicates the legal status or classification an entity held at the time it first arrived at a particular place or jurisdiction.
-
C.
hasBorderCrossingStatus
Indicates whether a border crossing is open, closed, restricted, or otherwise classified in terms of its operational or legal status.
-
D.
illegalityStatusAtDeparture
Indicates whether an entity’s departure from a location or jurisdiction was illegal at the time it occurred.
-
E.
borderCityStatus
Indicates that a city holds a designated status due to its location on or near a political or geographic border.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_6a00296249d48190b2de7af946126eaf |
completed | May 10, 2026, 6:44 a.m. |
Created at: May 3, 2026, 4:21 p.m.