Triple
T17730753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYPD 99th Precinct Detective Squad |
E442577
|
entity |
| Predicate | hasDetectiveRankMember |
P47925
|
FINISHED |
| Object | detective |
—
|
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: detective | Statement: [NYPD 99th Precinct Detective Squad, hasDetectiveRankMember, detective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectiveRankMember Context triple: [NYPD 99th Precinct Detective Squad, hasDetectiveRankMember, detective]
-
A.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
-
B.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
C.
admitsMemberRank
Indicates that an organization or group accepts individuals holding a specified rank or status as eligible members.
-
D.
isRank
chosen
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
E.
hasEnlistedRank
Indicates that an individual holds an enlisted (non-officer) rank within a military or similar hierarchical organization.
- 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_69e478e69f288190900027641952f198 |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.