Triple
T16739772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British order of precedence |
E406805
|
entity |
| Predicate | hasSeparateVersionFor |
P103241
|
FINISHED |
| Object | men |
—
|
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: men | Statement: [British order of precedence, hasSeparateVersionFor, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparateVersionFor Context triple: [British order of precedence, hasSeparateVersionFor, men]
-
A.
separateVersionsFor
chosen
Indicates that distinct versions must be maintained or handled separately for the related entities.
-
B.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
C.
hasSpecialVersion
Indicates that an entity possesses or is associated with a distinct or customized version of another entity, differing from the standard or default form.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
isExternalVersionOf
Indicates that one entity is a version or variant of another entity that exists or is maintained outside the primary or internal system or context.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3d4fa48190b0db8f10a39d3ad8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.