Triple
T9430661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TH 26 |
E227364
|
entity |
| Predicate | workMovementCount |
P11864
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [TH 26, workMovementCount, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workMovementCount Context triple: [TH 26, workMovementCount, 5]
-
A.
workMovement
Indicates a relationship where an entity’s work or employment involves changing physical locations, such as traveling or relocating as part of their job.
-
B.
numberOfMovements
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
C.
movementCount
chosen
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
D.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
E.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.