Triple
T33500261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Days Walking |
E857966
|
entity |
| Predicate | hasSequenceConcept |
P184838
|
FINISHED |
| Object | seven days |
—
|
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: seven days | Statement: [Seven Days Walking, hasSequenceConcept, seven days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSequenceConcept Context triple: [Seven Days Walking, hasSequenceConcept, seven days]
-
A.
hasTrackSequenceConcept
chosen
Indicates that one entity is associated with a conceptual representation of the ordered sequence of tracks or track elements related to it.
-
B.
hasSequenceRole
Indicates that one entity plays a specific functional or positional role within a biological or ordered sequence relative to another entity.
-
C.
usesSequence
Indicates that one entity employs or relies on a specific ordered sequence of elements, steps, or events in performing an action or defining a relationship.
-
D.
isSequence
Indicates that one entity is an ordered list or succession of elements arranged in a specific, meaningful order.
-
E.
isSequenceOf
Indicates that one entity occurs in a specific order directly following or as part of an ordered list relative to another entity.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:38 a.m.