Triple
T10134148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTAS.L |
E226812
|
entity |
| Predicate | isPassiveStrategy |
P23748
|
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: [FTAS.L, isPassiveStrategy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPassiveStrategy Context triple: [FTAS.L, isPassiveStrategy, true]
-
A.
isPassivelyManaged
chosen
Indicates that an entity (such as a fund or portfolio) is managed according to a passive strategy that tracks a benchmark or index rather than using active selection or frequent trading.
-
B.
usesStrategy
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
C.
isPartOfStrategy
Indicates that an action, component, or element belongs to, contributes to, or is included within a broader strategy.
-
D.
hasStrategicPass
Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
-
E.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
- 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_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. |
Created at: March 30, 2026, 9:06 p.m.