Triple
T16546705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three-Line Rifle |
E401960
|
entity |
| Predicate | hasFeedSystem |
P25552
|
FINISHED |
| Object | internal magazine |
—
|
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: internal magazine | Statement: [Three-Line Rifle, hasFeedSystem, internal magazine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeedSystem Context triple: [Three-Line Rifle, hasFeedSystem, internal magazine]
-
A.
feedSystem
Indicates that one entity supplies or provides input, resources, or data into another entity or system for its operation or processing.
-
B.
hasRSSFeeds
Indicates that an entity provides or is associated with one or more RSS feeds for distributing its content or updates.
-
C.
feederSystem
chosen
Indicates a system or mechanism that supplies or feeds resources, materials, or inputs into another process, component, or structure.
-
D.
hasFeederUnion
Indicates that an entity is associated with or connected to a feeder union, typically one that supplies members, resources, or support to it.
-
E.
feedsOn
Indicates that one entity obtains nourishment by consuming another entity as food.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.