Triple
T10134145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTAS.L |
E226812
|
entity |
| Predicate | replicatesAssetClass |
P92457
|
FINISHED |
| Object | UK equities |
—
|
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: UK equities | Statement: [FTAS.L, replicatesAssetClass, UK equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replicatesAssetClass Context triple: [FTAS.L, replicatesAssetClass, UK equities]
-
A.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
B.
overseesAssetClass
Indicates that one entity has responsibility for supervising, managing, or having authority over a particular asset class.
-
C.
assetClassesTraded
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
D.
replicaOf
Indicates that one entity is an exact or near-exact copy of another entity, preserving its form, structure, or content.
-
E.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd33808048190b6023a6cd83fc179 |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:06 p.m.