Triple
T3383990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Realty Investment Trust |
E71251
|
entity |
| Predicate | hasShareType |
P5725
|
FINISHED |
| Object | Common shares of beneficial interest |
—
|
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: Common shares of beneficial interest | Statement: [Federal Realty Investment Trust, hasShareType, Common shares of beneficial interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShareType Context triple: [Federal Realty Investment Trust, hasShareType, Common shares of beneficial interest]
-
A.
hasShareClass
chosen
Indicates that an entity is associated with a specific class or category of shares that defines distinct rights or characteristics of ownership.
-
B.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
C.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
D.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
E.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ec85d08190b28110157c39435f |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.