Triple
T16872940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkchester |
E421218
|
entity |
| Predicate | laterTenureType |
P22955
|
FINISHED |
| Object | condominium and cooperative ownership |
—
|
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: condominium and cooperative ownership | Statement: [Parkchester, laterTenureType, condominium and cooperative ownership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTenureType Context triple: [Parkchester, laterTenureType, condominium and cooperative ownership]
-
A.
tenureType
chosen
Indicates the type or category of tenure or contractual engagement that characterizes the relationship between the involved entities.
-
B.
isTenuredPosition
Indicates that a position is a permanent academic or professional role typically protected from arbitrary dismissal.
-
C.
endOfTenure
Indicates the point or event at which an entity’s period of holding a role, position, or office concludes.
-
D.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
-
E.
laterTerm
Indicates that one term occurs after another term in a temporal or sequential order.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f40410819088db22fa0d1eb808 |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.