Triple
T32888582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathfinder Project |
E841270
|
entity |
| Predicate | keyPersonnel |
P256
|
FINISHED |
| Object | Reginald Barclay |
—
|
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: Reginald Barclay | Statement: [Pathfinder Project, keyPersonnel, Reginald Barclay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPersonnel Context triple: [Pathfinder Project, keyPersonnel, Reginald Barclay]
-
A.
keyPerson
chosen
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
B.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
C.
keyMember
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
D.
keyOrganizationRole
Indicates that an organization holds a primary or defining role in relation to another entity or activity.
-
E.
personnel
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.