Triple
T11092996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CHS Field |
E262301
|
entity |
| Predicate | primaryTenantLevel |
P97191
|
FINISHED |
| Object | Triple-A |
—
|
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: Triple-A | Statement: [CHS Field, primaryTenantLevel, Triple-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTenantLevel Context triple: [CHS Field, primaryTenantLevel, Triple-A]
-
A.
primaryTenantTo
Indicates that one entity serves as the main or principal tenant in relation to another entity, such as a property or lease.
-
B.
primaryTenantFrom
Indicates that one entity serves as the main or principal tenant associated with another entity (such as a property or lease).
-
C.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
D.
intendedTenant
Indicates that one entity is designated or expected to occupy or lease another entity (such as a property) as a tenant.
-
E.
primaryTenantConference
Indicates that the subject entity is the main or lead tenant associated with a particular conference event or conference-related arrangement.
- F. None of above. chosen
Provenance (4 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ed12d88190a4ad8c346d68f11f |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.