Triple
T37555122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Constructs |
E933677
|
entity |
| Predicate | governsDomainOf |
P203667
|
FINISHED |
| Object | constructs |
—
|
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: constructs | Statement: [House of Constructs, governsDomainOf, constructs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsDomainOf Context triple: [House of Constructs, governsDomainOf, constructs]
-
A.
governedDomainType
Indicates that one entity establishes rules, control, or authority over a specific type or category of domain.
-
B.
domainGoverned
Indicates that one domain or territory is politically controlled, administered, or ruled by another authority or governing entity.
-
C.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
governsInRelationTo
chosen
Indicates that one entity exercises authoritative control, direction, or regulatory power over another entity within a specific relational or contextual framework.
-
E.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0356f541b08190b40469aa628087f4 |
completed | May 12, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_6a03569e4fa881909c57351a6c489636 |
completed | May 12, 2026, 4:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.