Triple
T35791259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scientific Study of Unidentified Flying Objects committee |
E1034695
|
entity |
| Predicate | reportCommonName |
P184659
|
FINISHED |
| Object | Condon Report |
—
|
NE NERFINISHED |
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: Condon Report | Statement: [Scientific Study of Unidentified Flying Objects committee, reportCommonName, Condon Report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportCommonName Context triple: [Scientific Study of Unidentified Flying Objects committee, reportCommonName, Condon Report]
-
A.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
B.
otherCommonName
Indicates that an entity is known by an additional, alternative common name besides its primary one.
-
C.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
D.
commonNameGroup
Indicates that multiple entities share the same commonly used name or are grouped under a single common name.
-
E.
moreCommonPublicName
Indicates that one name is used more frequently or popularly in public contexts than another alternative name for the same entity.
- F. None of above. chosen
Provenance (4 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:06 p.m.