Triple
T24769013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transylvania Company |
E619667
|
entity |
| Predicate | compensatedBy |
P26699
|
FINISHED |
| Object | Virginia |
—
|
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: Virginia | Statement: [Transylvania Company, compensatedBy, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compensatedBy Context triple: [Transylvania Company, compensatedBy, Virginia]
-
A.
compensated
chosen
Indicates that one entity provides payment or some form of recompense to another entity in return for goods, services, or loss incurred.
-
B.
compensatoryType
Indicates the specific category or nature of compensation associated with an action, obligation, or remedy in the relationship.
-
C.
compensationSetBy
Indicates that one party determines or establishes the compensation or pay level for another party.
-
D.
compensationReason
Indicates the reason or cause for which compensation is granted, requested, or applied between entities.
-
E.
compensationTrigger
Indicates the event or condition that initiates or authorizes a compensation or payment to be made.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:29 a.m.