Triple
T31762033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSC |
E810705
|
entity |
| Predicate | representsMarketSegment |
P146868
|
FINISHED |
| Object | UK small-cap 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 small-cap equities | Statement: [FTSC, representsMarketSegment, UK small-cap equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsMarketSegment Context triple: [FTSC, representsMarketSegment, UK small-cap equities]
-
A.
hasMarketSegmentFor
Indicates that an entity targets or serves a specific market segment for its products or services.
-
B.
marketSegmentType
chosen
Indicates the specific category or segment of the market that an entity, product, or service is targeted toward or associated with.
-
C.
governsMarketSegment
Indicates that an entity has controlling influence or regulatory authority over a particular market segment.
-
D.
marketSegmentPreviewed
Indicates that a specific market segment has been reviewed or examined in advance, typically as part of planning, analysis, or evaluation activities.
-
E.
separateMarketFrom
Indicates that one entity distinguishes or isolates a market from another context, system, or set of activities.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 30, 2026, 11:31 p.m.