Triple
T20528714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Egyptian period |
E504011
|
entity |
| Predicate | hasFormOfRule |
P140439
|
FINISHED |
| Object | condominium |
—
|
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 | Statement: [Anglo-Egyptian period, hasFormOfRule, condominium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormOfRule Context triple: [Anglo-Egyptian period, hasFormOfRule, condominium]
-
A.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
B.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
D.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
E.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
- F. None of above. chosen
Provenance (4 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06926248190942fc9608e6b85fd |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:37 a.m.