Triple
T5819189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fibra Uno |
E129064
|
entity |
| Predicate | hasFinancialInstrumentType |
P67141
|
FINISHED |
| Object | real estate trust certificates |
—
|
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: real estate trust certificates | Statement: [Fibra Uno, hasFinancialInstrumentType, real estate trust certificates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinancialInstrumentType Context triple: [Fibra Uno, hasFinancialInstrumentType, real estate trust certificates]
-
A.
hasLendingInstrument
Indicates that an entity possesses or utilizes a specific financial instrument used for lending.
-
B.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
-
C.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
D.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
E.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:53 p.m.