Triple
T17723838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josephine Archer Cameron |
E442407
|
entity |
| Predicate | basedOnPublicSources |
P114485
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Josephine Archer Cameron, basedOnPublicSources, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPublicSources Context triple: [Josephine Archer Cameron, basedOnPublicSources, yes]
-
A.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
B.
basedOnFactFrom
chosen
Indicates that something is derived, justified, or constructed using factual information obtained from a specified source.
-
C.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
D.
isOfficialSourceFor
Indicates that one entity is recognized as an authoritative or formally sanctioned provider of information or content about another entity.
-
E.
basedOnSourcesUpTo
Indicates that something is derived, justified, or determined using information available only up to a specified point in time.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4748900608190bf5ba04415edaffc |
completed | April 19, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.