Triple
T17239491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rensselaerswyck |
E418449
|
entity |
| Predicate | tenureSystem |
P22955
|
FINISHED |
| Object | semi-feudal manor |
—
|
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: semi-feudal manor | Statement: [Rensselaerswyck, tenureSystem, semi-feudal manor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenureSystem Context triple: [Rensselaerswyck, tenureSystem, semi-feudal manor]
-
A.
tenureType
chosen
Indicates the type or category of tenure or contractual engagement that characterizes the relationship between the involved entities.
-
B.
tenureCharacteristic
Indicates a relationship where a specific attribute or quality characterizes the duration or conditions of someone’s or something’s tenure.
-
C.
tenureDependsOn
Indicates that the duration or continuation of one entity’s tenure is conditional on or determined by another specified factor or entity.
-
D.
endOfTenure
Indicates the point or event at which an entity’s period of holding a role, position, or office concludes.
-
E.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfdc8688190aceb223c19a48781 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.