Triple
T28866569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Wilson |
E729015
|
entity |
| Predicate | notBelievedBy |
P76739
|
FINISHED |
| Object | flight crew |
—
|
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: flight crew | Statement: [Robert Wilson, notBelievedBy, flight crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notBelievedBy Context triple: [Robert Wilson, notBelievedBy, flight crew]
-
A.
declaresUnbeliefOn
chosen
Indicates that one entity explicitly states or affirms a lack of belief in, or rejection of, another entity.
-
B.
nonCreedal
Indicates that a religious group, belief system, or practice does not adhere to or require formal creeds or fixed doctrinal statements.
-
C.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
D.
maintainsBeliefDespite
Indicates that an entity continues to hold a particular belief even in the face of opposing evidence, pressure, or changing circumstances.
-
E.
believedBySomeToBe
Indicates that at least some people hold the belief that one entity has a particular property, status, or relationship to 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a1ca88c8190a6533eb95c8479d8 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:49 a.m.