Triple
T9927963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn family |
E187969
|
entity |
| Predicate | legalStatusInPennsylvania |
P2250
|
FINISHED |
| Object | proprietary family |
—
|
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: proprietary family | Statement: [Penn family, legalStatusInPennsylvania, proprietary family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInPennsylvania Context triple: [Penn family, legalStatusInPennsylvania, proprietary family]
-
A.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
B.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
C.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
-
D.
legalStatusAccordingToIndia
Indicates the legal status or classification of an entity as defined specifically by the laws and regulations of India.
-
E.
legalStatusVariesBy
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb59d7ad08190982a1584547190bd |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.