Triple
T38394750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosings Park |
E900724
|
entity |
| Predicate | hasNotableOwnerTrait |
P167169
|
FINISHED |
| Object | owner is domineering |
—
|
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: owner is domineering | Statement: [Rosings Park, hasNotableOwnerTrait, owner is domineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableOwnerTrait Context triple: [Rosings Park, hasNotableOwnerTrait, owner is domineering]
-
A.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
-
B.
hasOwnerTrait
chosen
Indicates that an owner possesses or exhibits a specific trait or characteristic.
-
C.
hasNotablePropertyIn
Indicates that an entity possesses a specific notable property or characteristic within a particular context, domain, or scope.
-
D.
hasNotablePromoter
Indicates that an entity is actively supported, publicized, or championed by a notable promoter.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.