Triple
T26556526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Related Rentals |
E666122
|
entity |
| Predicate | managesPropertiesOwnedBy |
P102059
|
FINISHED |
| Object | Related Companies |
—
|
NE NERFINISHED |
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: Related Companies | Statement: [Related Rentals, managesPropertiesOwnedBy, Related Companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesPropertiesOwnedBy Context triple: [Related Rentals, managesPropertiesOwnedBy, Related Companies]
-
A.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
B.
numberOfPropertiesManaged
Indicates the total count of properties that an entity is responsible for managing.
-
C.
managesPropertyFor
chosen
Indicates that one entity is responsible for overseeing, operating, or administering a property on behalf of another entity.
-
D.
ownedPropertyWith
Indicates a relationship where one entity owns a particular property jointly or in association with another entity.
-
E.
ownsOrManages
Indicates that one entity has ownership of, or managerial control over, 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 1:50 a.m.