Triple
T22149863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summa Corporation |
E547383
|
entity |
| Predicate | roleInRealEstate |
P126569
|
FINISHED |
| Object | major landholder in Nevada |
—
|
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: major landholder in Nevada | Statement: [Summa Corporation, roleInRealEstate, major landholder in Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRealEstate Context triple: [Summa Corporation, roleInRealEstate, major landholder in Nevada]
-
A.
estateRole
Indicates the specific function, capacity, or responsibility an entity holds in relation to an estate (such as owner, executor, or beneficiary).
-
B.
realEstate
chosen
Indicates a relationship where an entity owns, manages, or is otherwise associated with real property such as land or buildings.
-
C.
realEstateCategory
Indicates the classification of a property into a specific type or category within real estate (e.g., residential, commercial, industrial).
-
D.
roleInMLS
Indicates that an entity holds or has held a specific role or position within Major League Soccer (MLS).
-
E.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f2c0e881909c3488bb5eb5959d |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.