Triple
T36571894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandywine Realty Trust |
E902141
|
entity |
| Predicate | isIncomeProducing |
P33727
|
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: [Brandywine Realty Trust, isIncomeProducing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIncomeProducing Context triple: [Brandywine Realty Trust, isIncomeProducing, true]
-
A.
usesForIncome
Indicates that one entity derives income or financial gain from using another entity.
-
B.
isIncomeStock
chosen
Indicates that a stock primarily generates regular income (such as dividends) rather than being held mainly for capital appreciation.
-
C.
hasEconomicActivity
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
D.
incomeType
Indicates the category or source classification of an entity’s income within a given context.
-
E.
income
Indicates the amount of money an entity receives, typically over a specified period, from work, investments, or other sources.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.