Triple
T32392193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUA:IND |
E827700
|
entity |
| Predicate | hasBaseUniverse |
P168585
|
FINISHED |
| Object | U.S. investable equity market |
—
|
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: U.S. investable equity market | Statement: [RUA:IND, hasBaseUniverse, U.S. investable equity market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseUniverse Context triple: [RUA:IND, hasBaseUniverse, U.S. investable equity market]
-
A.
hasBaseSpace
chosen
Indicates that one entity is defined or structured with respect to another entity that serves as its underlying base space.
-
B.
basedInUniverseOn
Indicates that something is set or takes place within a fictional universe that is derived from, inspired by, or adapted from another source.
-
C.
hasBaseRegion
Indicates that one entity is situated upon, supported by, or primarily associated with a specific underlying region or area.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 12:52 a.m.