Triple
T31183631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schedule E |
E794969
|
entity |
| Predicate | governsActivityType |
P20949
|
FINISHED |
| Object | passive income |
—
|
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: passive income | Statement: [Schedule E, governsActivityType, passive income]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsActivityType Context triple: [Schedule E, governsActivityType, passive income]
-
A.
hasActivityType
chosen
Indicates the specific kind or category of activity associated with an entity or event.
-
B.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
C.
governsAssetType
Indicates that one entity has authority or control over the rules, usage, or management of a particular type or class of asset.
-
D.
governsOfficeType
Indicates that an entity has authoritative control or regulatory oversight over a particular type or category of office.
-
E.
governsAssessmentType
Indicates that one entity determines, regulates, or controls the type or method of assessment applied to 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: April 29, 2026, 9:08 p.m.