Triple
T32993181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | beguine court |
E844146
|
entity |
| Predicate | hasPropertyRule |
P23698
|
FINISHED |
| Object | individual residents could own property |
—
|
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: individual residents could own property | Statement: [beguine court, hasPropertyRule, individual residents could own property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyRule Context triple: [beguine court, hasPropertyRule, individual residents could own property]
-
A.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
C.
hasRuleCharacteristic
Indicates that something possesses a specific property, feature, or attribute related to a rule or set of rules.
-
D.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
E.
hasPropertyT
Indicates that an entity possesses or is characterized by a specific property T.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a013b78bde881909a082beced4e0157 |
completed | May 11, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a013acf45508190a999b208066072bd |
completed | May 11, 2026, 2:11 a.m. |
Created at: May 1, 2026, 1:22 a.m.