Triple
T37459822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Quarter |
E930889
|
entity |
| Predicate | hasClassChallenge |
P195882
|
FINISHED |
| Object | Warrior |
—
|
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: Warrior | Statement: [Military Quarter, hasClassChallenge, Warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassChallenge Context triple: [Military Quarter, hasClassChallenge, Warrior]
-
A.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
B.
hasBeenChallengedIn
Indicates that an entity has faced a challenge, contest, or dispute within a specified context, domain, or setting.
-
C.
hasBeenChallengedFor
Indicates that an entity has been formally questioned, disputed, or contested specifically in relation to another entity or issue.
-
D.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
E.
hasMandatoryChallengerSystem
Indicates that an entity is required to implement or participate in a challenger system, where challenges must be accepted or processed according to defined rules.
- F. None of above. chosen
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4:17 p.m.