Triple
T35047831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rambler Crest |
E1011248
|
entity |
| Predicate | hasManagementOffice |
P23722
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rambler Crest, hasManagementOffice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagementOffice Context triple: [Rambler Crest, hasManagementOffice, true]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
hasCorporateOffice
Indicates that an entity maintains a formal corporate office at a specified location or within another organizational entity.
-
C.
hasTopOffice
Indicates that an entity holds the highest-ranking office or position within a specified organization, institution, or jurisdiction.
-
D.
hasSupportingOffice
chosen
Indicates that an entity is associated with or served by a particular office that provides support or administrative services to it.
-
E.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01e993fec0819090cc397218515e88 |
completed | May 11, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_6a01e57594188190a2354f48cf71b48c |
completed | May 11, 2026, 2:19 p.m. |
Created at: May 3, 2026, 4:01 p.m.