Triple
T5135067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Shepherd |
E115798
|
entity |
| Predicate | workingDrive |
P62816
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Dutch Shepherd, workingDrive, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingDrive Context triple: [Dutch Shepherd, workingDrive, strong]
-
A.
notableDrive
Indicates that an entity is particularly recognized or distinguished for its driving performance, experience, or characteristics.
-
B.
driveContext
Indicates that one entity is operating or controlling a vehicle or mode of transport within a particular situational or environmental context.
-
C.
officeMergedInto
Indicates that one office has been combined with and absorbed into another office, ceasing to exist as a separate entity.
-
D.
officeWebsite
Indicates that the website referenced is the official online site associated with a particular office or officeholder.
-
E.
officeScope
Indicates that a relationship, authority, or action is limited to, defined within, or applicable only in the context of a particular office or official position.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7fee42748190967013828973cce0 |
completed | March 20, 2026, 5:12 p.m. |
Created at: March 20, 2026, 1:43 p.m.