Triple
T1737410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCIS |
E37949
|
entity |
| Predicate | typicalEpisodeStructure |
P20979
|
FINISHED |
| Object | case-of-the-week |
—
|
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: case-of-the-week | Statement: [NCIS, typicalEpisodeStructure, case-of-the-week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEpisodeStructure Context triple: [NCIS, typicalEpisodeStructure, case-of-the-week]
-
A.
hasEpisodeStructure
chosen
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
B.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
C.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
D.
numberOfEpisodes
Indicates the total count of episodes associated with a given entity, such as a series or season.
-
E.
directedEpisodeOf
Indicates that a person served as the director for a specific episode of a television or web series.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.