Triple
T32446985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Penn |
E829174
|
entity |
| Predicate | propertyInterestIn |
P163088
|
FINISHED |
| Object | proprietary lands in Pennsylvania |
—
|
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 lands in Pennsylvania | Statement: [John Penn, propertyInterestIn, proprietary lands in Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyInterestIn Context triple: [John Penn, propertyInterestIn, proprietary lands in Pennsylvania]
-
A.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
B.
propertyHeld
chosen
Indicates that a particular property is possessed, owned, or controlled by a specified entity.
-
C.
propertySystem
Indicates that one entity functions as a property or attribute system governing or organizing the properties of another entity.
-
D.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
E.
studiedProperty
Indicates that an entity has examined, researched, or analyzed a particular property or attribute of another entity.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 12:56 a.m.