Triple
T22180473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FUNO |
E548154
|
entity |
| Predicate | underlyingEntityType |
P110019
|
FINISHED |
| Object | real estate investment trust |
—
|
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 investment trust | Statement: [FUNO, underlyingEntityType, real estate investment trust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingEntityType Context triple: [FUNO, underlyingEntityType, real estate investment trust]
-
A.
hasUnderlyingEntity
chosen
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
-
B.
includedEntityType
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
C.
identifiesEntityType
Indicates that one entity specifies or determines the type or category to which another entity belongs.
-
D.
documentedEntityType
Indicates that an entity has been documented as belonging to a specific type or category.
-
E.
appliedToEntityType
Indicates that something (such as a rule, constraint, or operation) is specifically applied to entities of a given type.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa4d4ac8190922b919c15623963 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.