Triple
T4440084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elon Musk Revocable Trust |
E95748
|
entity |
| Predicate | publicInformationSource |
P2296
|
FINISHED |
| Object | regulatory filings |
—
|
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: regulatory filings | Statement: [Elon Musk Revocable Trust, publicInformationSource, regulatory filings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicInformationSource Context triple: [Elon Musk Revocable Trust, publicInformationSource, regulatory filings]
-
A.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
B.
intelligenceSource
Indicates that one entity serves as the origin or provider of intelligence information for another entity.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
E.
primarySources
chosen
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355ac05e081908411089c05fc36bd |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.