Triple
T3199110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fighting Fifth |
E67002
|
entity |
| Predicate | nicknameForUnitType |
P40066
|
FINISHED |
| Object | regiment |
—
|
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: regiment | Statement: [Fighting Fifth, nicknameForUnitType, regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameForUnitType Context triple: [Fighting Fifth, nicknameForUnitType, regiment]
-
A.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by another entity.
-
B.
hasNicknamedEntityType
chosen
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
C.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
D.
typicalTeamDesignation
Indicates the standard or commonly used team name or label that is typically assigned to an entity.
-
E.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9abe8f88190a4c2ccc31add7959 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.