Triple
T10529444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detective Chief Inspector |
E248396
|
entity |
| Predicate | typicallyHeads |
P652
|
FINISHED |
| Object | major investigation team |
—
|
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: major investigation team | Statement: [Detective Chief Inspector, typicallyHeads, major investigation team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyHeads Context triple: [Detective Chief Inspector, typicallyHeads, major investigation team]
-
A.
heads
chosen
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
B.
coHeads
Indicates that two or more entities jointly hold the primary leadership or head position of the same organization, group, or initiative.
-
C.
usuallyHears
Indicates that one entity typically or habitually perceives sounds produced by another entity.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicallySpared
Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f7d8ac8190b90c1a7f77b23545 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.